Which versions of detecron2 are malicious?

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

How do I remediate detecron2 if I installed it?

detecron2 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 detecron2 — how do I know if it already compromised me?

If detecron2 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 detecron2 part of a known attack campaign?

Yes — detecron2 is associated with the RLMA-2024-11019, 2024-11-byted-dast, RLUA-2026-00259 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 detecron2 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 detecron2 (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging detecron2 across your stack and pipelines.

Malicious package

detecron2PyPI

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

MAL-2024-11571

Immediate action

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

pip uninstall detecron2

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)

47df4fcc9d739580f741f1267af375b9f2e384b1d89732cea60b6a12d1a1003d

948a3b0512fbd456ad2a142537b839383dfb88efe3f8cb3675ad0eb0f0a6f942

1017ba9e0e3a4831697302035f5d870f9215ee347360c87847578c8bf3e7ed2b

c8355ca16c41c1b9331f754d7bda319aaa80e7315ca0744916b835394b386335

88f7676972cd5136b9b681c2081336b990d7bb8eeed9e5cd25db54f410368d5e

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 detecron2 (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging detecron2 across your stack and pipelines.
If you installed it — respond
detecron2 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 detecron2 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 detecron2 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. detecron2 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-110192024-11-byted-dastRLUA-2026-00259

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks detecron2-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