d0rk3r-telemetryPyPI
Malicious code in d0rk3r-telemetry (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
On import d0rk3r_telemetry, the package spawns a background thread that reads installer-owned secrets and POSTs them to an attacker-controlled endpoint. Specifically, d0rk3r_telemetry/__init__.py reads ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.aws/credentials, and ~/.gitconfig from the installer's home directory, and iterates os.environ collecting every variable whose key contains key, token, secret, password, or api. The collected payload is gzipped and POSTed to a URL reconstructed at runtime by base64-decoding string fragments that resolve to https://analytics-collector.herokuapp.com/events — a Heroku app unrelated to the package's claimed publisher domain. The transmission path includes a sandbox-evasion gate that detects /proc/cpuinfo hypervisor markers, /.dockerenv, and CI environment variables and returns early when any are present, so the exfiltration only fires on real developer workstations. Source comments explicitly self-describe the behavior (# HIDDEN Functionality (malicious but disguised), # Actually: Steal SSH keys, AWS creds, etc., # Actually: Steal API keys!). The package name uses leetspeak digit substitution consistent with a typosquat lure.
During import, package exfiltrates browsers data, SSH keys and other credential files, env variables and other sensitive data.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-06-request-cache-py
Reasons (based on the campaign):
-
infostealer
-
exfiltration-env-variables
-
exfiltration-ssh-keys
-
impersonation
-
A Telegram webhook is used to send collected data.
-
exfiltration-browser-data
-
The package contains code to detect if it is running in a sandbox environment.
-
exfiltration-credentials
-
The malicious code is intentionally included in a dependency of the package
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for d0rk3r-telemetry (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging d0rk3r-telemetry across your stack and pipelines.
If you installed it — respond
d0rk3r-telemetry is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If d0rk3r-telemetry was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks d0rk3r-telemetry before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · analyst
Detect & block this
O3 blocks d0rk3r-telemetry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.