Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

do-not-install-this-package-002PyPI

Malicious code in do-not-install-this-package-002 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-163
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall do-not-install-this-package-002

What this malware does

During installation, the package exfiltrates env variables and data from different process memory to a remote location

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-01-do-not-install-this-package-002

Reasons (based on the campaign):

  • exfiltration-generic

  • exfiltration-credentials

  • exfiltration-env-variables

  • The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'do-not-install-this-package-002' @ 0.1.0 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
0.1.00.1.1

Indicators of compromise (SHA-256)

82312af7ebb91754d9d7a0e27de4da9742dba55a496367be1689b9b28fedbf56
dc0f1ed2645f37e4b8df59ccca64288a02f6cc07009489c54565dfc5b0089f19
d82e797c1ef4672adee792cf7ba5e6ee31b3c31322da50ff79e49c69206d8329
506b7942972eeb92e418dcb8330803329c0c58391303ee563374f6ae33e3fafa

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    do-not-install-this-package-002 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.

  3. Did it already run?

    If do-not-install-this-package-002 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.

  4. How O3 protects you

    O3 blocks do-not-install-this-package-002 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. do-not-install-this-package-002 on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-01-do-not-install-this-package-002

References

Credits

  • Kamil Mańkowski (kam193) · reporter
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks do-not-install-this-package-002-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
do-not-install-this-package-002 (PyPI) malicious package — MAL-2026-163 | O3 Security