Which versions of d5e54nc32y1337 are malicious?

The following PyPI versions of d5e54nc32y1337 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate d5e54nc32y1337 if I installed it?

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

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

Yes — d5e54nc32y1337 is associated with the RLMA-2025-01208, GENERIC-standard-pypi-install-pentest, RLUA-2026-00244 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 d5e54nc32y1337 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 d5e54nc32y1337 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging d5e54nc32y1337 across your stack and pipelines.

Malicious package

d5e54nc32y1337PyPI

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

MAL-2025-1968

Immediate action

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

pip uninstall d5e54nc32y1337

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1b4b40139d87eeba1991cb90732401af2b4bf21748a37c42669b04a65128906c

c4f6d67e0e4c37d4dafcdd1ea042329a02046645a5128110ed76b4070bd676d4

13cd8ff22129444670c5269677ecf7d1321f469f42b693571b5726537e1ffcec

c1199c2dd8d815ee05716fc8869560cb8c32046ece39b55c835b949620e3af2b

7f2697243b98f3a9950578a7c2323a91cf55f96f5f041c2022eb53b73bc74afa

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

Campaign

RLMA-2025-01208GENERIC-standard-pypi-install-pentestRLUA-2026-00244

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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