Server Access Setup
How to grant secure SSH access for malware investigation and cleanup
Our SSH Public Key
To investigate and clean your server, we need SSH access. Add the following public key to the server. This only grants access to whoever holds the matching private key — which is only me.
This key is rotated every six months for security. The key shown above is always the current one. If you have an older key on file, please replace it with this one.
How to Add the Key
Choose the method that matches your hosting environment:
cPanel / WHM
- Log in to cPanel
- Go to
Security→SSH Access→Manage SSH Keys - Click
Import Key - Leave the key name as default, paste the public key into the Public Key field
- Click
Import, then go back and clickManage→Authorize
For root access (WHM): navigate to WHM → Security Center → Manage root's SSH Keys
Plesk
- Log in to Plesk as admin
- Go to
Tools & Settings→SSH Keys(under Security) - Click
Add Key - Paste the public key into the Key content field
- Click
Add
For subscription-level access: Domains → [domain] → SSH Access
DirectAdmin
- Log in to DirectAdmin as admin
- Go to
SSH Keys(under Account Manager or Admin Tools) - Click
Create KeyorPaste Key - Paste the public key and save
Manual (SSH Command Line)
If you have SSH access to the server, run the following command as the user we need to connect as (typically root):
Where We Connect From
All SSH connections originate exclusively from our dedicated jump server. You can whitelist this host in your firewall to restrict access to only our infrastructure:
Jump Server
Hostname: baremetal.kbourdakos.gr
IPv4: 147.135.213.177
IPv6: 2001:41d0:303:6fb1::1
This is a dedicated bare-metal server under our direct control — not shared hosting, not a cloud instance. All connections are logged and auditable.
Optional but recommended: Configure your firewall to allow SSH from 147.135.213.177 and 2001:41d0:303:6fb1::1 only during the engagement period. Security is our first priority.
Custom SSH Port?
If your server runs SSH on a port other than 22, please let me know the port number when granting access. If you've configured a firewall whitelist for our IP, make sure it covers your custom port, not just port 22.
What Access We Need
- Root or sudo access is ideal — it allows me to inspect all accounts, check crontabs, review system logs, and perform thorough cleanup across the entire server.
- Account-level access (e.g. the cPanel user account) works for single-site cleanups, but limits visibility into server-wide compromise indicators.
- We will tell you which level is needed based on the incident.
What We Will and Won't Do
Security Guarantees
- Investigation phase is strictly read-only — no files are modified until you approve the remediation plan
- All actions are documented and included in the final report
- Malicious files are backed up to an evidence directory before deletion — nothing is lost
- We will never access unrelated accounts, databases, or data outside the scope of the investigation
- NDA available upon request
After the Job
Once the cleanup is complete and you've received the report:
- Remove our SSH key from the server using the same panel where you added it
- We'll confirm removal is done on our end as well
- No persistent access is retained — the key only works while it's in your
authorized_keys
If we work together regularly, you can keep the key in place and revoke it anytime. You're always in control.
Alternative: Share Credentials via Vault
If adding an SSH key isn't practical for your setup, you can securely share your server credentials through our self-hosted Vault instead:
How It Works
- We'll send you a secure link via vault.kbourdakos.gr
- You fill in your server details (IP, SSH port, username, password or key)
- The data is end-to-end encrypted and only accessible by me
- No credentials are sent over email or chat in plain text
Vault is hosted on our own dedicated infrastructure — no third-party services involved.
Questions?
If you're unsure about any step or want to discuss access scope before granting it, get in touch and we'll figure it out together.