Which versions of detectron4 are malicious?

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

How do I remediate detectron4 if I installed it?

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

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

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

Malicious package

detectron4PyPI

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

MAL-2024-11573

Immediate action

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

pip uninstall detectron4

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)

ed2041190645121664b94af723b241783e2b6a884069d1d79afc9eacac8b451c

b7af4e540c2a5a3684a3a582b8dea568664d51d5dc7ae8bcd1b81483e5f523c8

65b386bb525d3578f1345cf715ede6e58c9aae5fe31200cb381ac39ff51415e2

40e1dbf6987b12680f1e7e80ddecca355b636398e72045063e95ca18c16c4c4b

afd7b2f0d30e29c9569afac980fbd3d469ffefd0d96f942c49bf78fcde2dddad

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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