Which versions of detectren are malicious?

The following PyPI versions of detectren are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate detectren if I installed it?

detectren 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.

I already installed detectren — how do I know if it already compromised me?

If detectren 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.

Is detectren part of a known attack campaign?

Yes — detectren is associated with the RLMA-2024-11020, 2024-11-byted-dast, RLUA-2026-00260 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find detectren across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for detectren (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging detectren across your stack and pipelines.

Malicious package

detectrenPyPI

Malicious code in detectren (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11572

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall detectren

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

94.6

Indicators of compromise (SHA-256)

8c17d53c1e872b714fcaf0abd2788d9aa26f6410770395fac81fb207d0421fbd

a341f146bb075ad1666185a44843cc8e0d5d2abee90218a7e7475fd55a7fc357

d10bdb7431221aa1a0844eb0632c2e2e7be5fb7033dfbdb305e071160bd1b574

0bd155cd751e4a0f8c4b6e1fc1859b3be0adef4a81bcffe080814c063fe9736f

b566b1f2778182d7a637b30c82853f04676f418a89f638eed9c77bce9e956a2e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for detectren (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging detectren across your stack and pipelines.
If you installed it — respond
detectren 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 detectren 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 detectren 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

No. detectren on PyPI has been identified as a malicious package (version 94.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-110202024-11-byted-dastRLUA-2026-00260

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks detectren-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring