Which versions of d1n0-exploit-aaaa are malicious?

The following PyPI versions of d1n0-exploit-aaaa are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate d1n0-exploit-aaaa if I installed it?

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

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

Yes — d1n0-exploit-aaaa 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 d1n0-exploit-aaaa 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 d1n0-exploit-aaaa (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging d1n0-exploit-aaaa across your stack and pipelines.

Malicious package

d1n0-exploit-aaaaPyPI

Malicious code in d1n0-exploit-aaaa (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191710

Immediate action

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

pip uninstall d1n0-exploit-aaaa

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c5da1a696e114b609cd08c52de1bb1b10b2477ed3e5c670c7821206757310863

64210508ed5694fbb8abfa75dbca12a3f6a0ebc0b653866d6fd01de23cdc5170

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 d1n0-exploit-aaaa (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging d1n0-exploit-aaaa across your stack and pipelines.
If you installed it — respond
d1n0-exploit-aaaa 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 d1n0-exploit-aaaa 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 d1n0-exploit-aaaa 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. d1n0-exploit-aaaa on PyPI has been identified as a malicious package (version 0.0.1 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 d1n0-exploit-aaaa-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