Staying Anonymous
Every connection you make leaves a trace. Law enforcement actively investigates cyber crimes, and if they trace you back to your real location they trigger a Federal Raid. This guide is the trace loop: how investigations build, how to clean up, and what the panic window buys you. For how scans get flagged in the first place, and for proxychains, see Scanning & Stealth.
Stealth and traces
Section titled “Stealth and traces”Trace mechanics
Section titled “Trace mechanics”When you perform suspicious actions, an investigation begins. The trace timer ticks every 10 seconds, following your connection chain back through the network logs. The investigation indicator on your taskbar shows your status:
| Indicator | Meaning |
|---|---|
| Green | No active investigations |
| Amber | Investigation in progress, be cautious |
| Red | Trace is close, take immediate action |
Heat is your overall notoriety. It builds from hacking activities and decays over time. Higher heat means faster traces and more severe consequences.
Cleaning your trail
Section titled “Cleaning your trail”logcleaner removes your trail from a server’s logs. The surgical form is the default on every box and every hop:
| Command | What it does |
|---|---|
logcleaner --ip <your_ip> |
Removes only the log entries naming you (plus burner IPs that carried your traffic during LTE failover). User level, no root, costs no heat, opens no investigation, no dual-track penalty |
logcleaner --selective <text> |
Removes entries plus /var/log lines matching text (--regex for a pattern). Also surgical |
logcleaner --time <min> |
Removes entries within a time window. Also surgical |
logcleaner --all |
Truncates every log file. Needs root and flips the dual-track check to tampered, giving the trace walker a 1.5x speed boost on that box for the rest of the operation. Only reach for it when you have already been named |
Doing --all then rm takes the tampered penalty twice.
Optimal loop: work -> logcleaner --ip <your_ip> -> disconnectOn a proxy chain, walk it in reverse and run the surgical clean on every hop before dropping the sessions.
Investigation and diversion commands
Section titled “Investigation and diversion commands”| Command | What it does |
|---|---|
analyze |
View active investigations, heat, and trace status |
analyze --deep |
Full dossier: trace position, ETA, evidence, countermeasures |
analyze --redirect <ip> |
Redirect the closest trace to a decoy server (needs root on target, +0.15 heat) |
analyze --tipoff <rival> |
Anonymous tip, opens an investigation on a rival’s home server (+0.2 heat) |
rep |
Quick overview of your current heat and investigations |
failover |
LTE burner IP rotation, stalls traces temporarily |
strobe |
IoT manipulation, creates trace diversions |
Going dark: security agents
Section titled “Going dark: security agents”Any box on a LAN with a SIEM, IPS, or IDS appliance runs a security agent reporting to that collector. While the agent is alive, a trace running through the box moves faster. Find it with ps and ss (sockstat on FreeBSD): look for the agent process (splunkd to a SIEM, ampdaemon to a Cisco IPS, filebeat to a Suricata IDS, syslog-ng on gateways and FreeBSD) plus an ESTABLISHED socket to the collector.
kill /var/run/<agent>.pidThis stops the forwarder and the box goes dark, so the trace loses its speed-up. It needs root (the forwarder runs as root, so escalate first with linpeas then sudo, or kexploit).
The kill leaves one line in /var/log/syslog. Disconnect with it still there and the SIEM notices the dead agent and files a strike. logcleaner --ip will not catch it, because the line does not name your IP. Clear it with logcleaner --selective on the marker instead.
Go-dark loop: kill /var/run/<agent>.pid -> work -> cat /var/log/syslog (find the marker) -> logcleaner --selective <marker> -> disconnectWhen they fight back
Section titled “When they fight back”Serious networks have live defenders. On a monitored box an analyst logs in when an investigation opens and hunts you in real time: watch for them in w, ps and last, and for a wall broadcast as they close in.
If they catch you while you are loud (killing their security agent or antivirus, deploying a miner or botnet, or exfiltrating heavily) they contain the host: your session is cut and your source IP is firewall-blocked. Recover by going dark first with logcleaner --ip <your_ip> so they lose the thread, or, if you are already blocked, failover or proxychains to a new source, or wait the block out. Who these defenders are, and how to turn them into targets: SOC & Blue Team.
The Federal Raid
Section titled “The Federal Raid”If a trace completes, a Federal Raid is triggered:
- Your hot wallet balance is seized.
- Active investigations are cleared.
- Any property you bought is seized, and you are back in the basement.
- Heat is reset, but you are monitored for a while.
Getting caught is a setback, not game over.
The panic window
Section titled “The panic window”A raid does not land the instant the trace completes. There is a short panic window between the alert and the seizure, and two commands exist only inside it. Each works once:
| Command | What it does |
|---|---|
lockwallet |
Encrypts and scatters the hot wallet, so the seizure finds nothing |
shred --all |
Wipes incriminating local data (software licences survive) |
Outside a raid alert both refuse, reporting no active threat. Cold storage and your hardware are never at risk either way. If the alert fires and you do nothing, you lose the hot balance and your local files.
The Cold Room
Section titled “The Cold Room”A ransomware job is finished the moment the payload lands. You deliver it with upload to the target, which completes the contract and pays you. The Cold Room is the optional second act: a private channel where the victim can be pushed to pay more on top. It is never required. Walk away and you keep everything the contract already paid.
Mind the scanner
Section titled “Mind the scanner”The payload is live code, so a box running clamd quarantines it on upload, the same as a miner or a bot implant. If the deploy bounces, kill clamd first, then upload clean.
The channel
Section titled “The channel”When you disconnect and the contract banks, the victim reaches out by MeshMail and a case opens at coldroom.onion. Open that address in the browser to see it. There is no card for it on any site list, so go straight to the address. It is a chat thread with a named victim, a countdown, and a demand. You do not type free text: you pick moves, and the victim reacts.
Your moves
Section titled “Your moves”| Move | Effect |
|---|---|
| Prove you can decrypt | Good faith, raises their willingness to pay |
| Raise the demand / Hold firm | Push for more, at the cost of their patience |
| Ease off | Lower the number to keep them at the table |
| Threaten to leak the data | Heavy pressure, and the fastest way to spook them |
| Accept their offer (settle) | Take the current number and close out |
| Close the channel (walk) | End it with no extra payout |
Reading the room
Section titled “Reading the room”A willingness meter runs under the surface. Good-faith moves raise it, pressure spends it. Push a frightened victim too far and they stop negotiating and report it instead, which closes the case with nothing and leaves a trail. The deadline is real: let the countdown run out and the window is gone.
A settlement pays in BTC, but it is dirty and traceable like any coin that moves through you. Tumble it before you lean on it. The Cold Room is upside on a job already done, so play it for the extra, not for the rent.
Where to go next
Section titled “Where to go next”- Scanning & Stealth for the detection model and
proxychains. - Free Roam & the World Map to watch a trace draw in real time.
- Missions & Covert Ops for the contracts that generate the heat.
