Which versions of d1n0exploitaaaa are malicious?

The following PyPI versions of d1n0exploitaaaa are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate d1n0exploitaaaa if I installed it?

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

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

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

Malicious package

d1n0exploitaaaaPyPI

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

MAL-2025-191711

Immediate action

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

pip uninstall d1n0exploitaaaa

What this malware does

Importing the module starts a reverse shell

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

Campaign: 2025-11-d1n0

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

c66e94709b8d9f6dfd14c6e007a252df7b5c2ba40475f5f056f834bbf96e9d6d

7ecd01d9010a3e9192c6636d4ddefa1e493438b1bbf65002e8daf6a014067692

ec1c99ded21ce7edd996da88276b3654f3ac1872c43807c5d79e942297ac95f2

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

Campaign

2025-11-d1n0

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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