Which versions of maliciouspackage are malicious?

The following PyPI versions of maliciouspackage are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5. Treat any of these as compromised.

How do I remediate maliciouspackage if I installed it?

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

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

Yes — maliciouspackage is associated with the 2024-10-old-maliciouspackage 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 maliciouspackage 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 maliciouspackage (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging maliciouspackage across your stack and pipelines.

Malicious package

maliciouspackagePyPI

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

MAL-2024-12303

Immediate action

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

pip uninstall maliciouspackage

What this malware does

Clearly a demo malicious package, attempting to exfiltrate a token from the git config

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-10-old-maliciouspackage

Reasons (based on the campaign):

exfiltration-generic

Malicious versions

5 flagged

0.10.20.30.40.5

Indicators of compromise (SHA-256)

a17fbba816fdf42b4bdac0d9a16ad4ec7dacfbc367a4f57bfd936d2239b88917

d0e8a8d581266436f0546b5039ee82ab734d45f8489e281322dd871124dad9ce

1829cac32365b4cacd5c304a6efc6a7bab4e65f48c7e7f3fc2d598a2e62a5715

1a98553a381d9f9e235b782ea1a5f5d1c66e903d32df86b73588abc2070143bd

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 maliciouspackage (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging maliciouspackage across your stack and pipelines.
If you installed it — respond
maliciouspackage 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 maliciouspackage 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 maliciouspackage 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. maliciouspackage on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4, 0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-10-old-maliciouspackage

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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