Which versions of d1snakegame are malicious?

The following PyPI versions of d1snakegame are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate d1snakegame if I installed it?

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

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

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

Malicious package

d1snakegamePyPI

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

MAL-2025-191712

Immediate action

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

pip uninstall d1snakegame

What this malware does

The package starts a Discord bot that waits for messages and automatically executes any file sent as an attachment, effectively turning the package into a RAT.

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

Campaign: 2025-10-d1snakegame

Reasons (based on the campaign):

Downloads and executes a remote malicious script.

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

e5c0e77518a9f0ef47ce194e3cd485f8b4101dad1e01b97b8d9140b23c0d95fb

8023a44d657b04f09628c938fa7fb4fbd8c1300f630aff31837b32f2337ce65f

4538fa0d65a0e9983870ff8be4937121fbcc7ec186e2953112bae0f26e430ca6

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

Campaign

2025-10-d1snakegame

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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