Contain
On the day of discovery we blocked outbound traffic from the affected account, which cut off the miner, the Tor traffic and the proxy client. We disabled the open database login rule and restricted SSH to the company VPN.
The application stayed online throughout.
Preserve
We took a provider snapshot of the server as the primary forensic copy, then collected processes, network state, scheduled tasks, services, accounts and logs. The archives were copied off the server and hashed.
The malware was left in place as evidence.
Scope
A read-only review inventoried the software stack, services, environment variables, scheduled jobs and credentials, and ranked the findings by risk.
Every secret on the server was treated as exposed and queued for rotation.
Build Clean
We chose to replace the server instead of cleaning it. A new hardened server was built the same evening: SSH through the VPN only, key-only logins, an intrusion-prevention service and automatic updates.
Cut Over
The database moves as a plain SQL dump, reviewed before restore, under new credentials. Nothing else is copied from the old server.