Which versions of legendevil1 are malicious?

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

How do I remediate legendevil1 if I installed it?

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

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

Yes — legendevil1 is associated with the 2025-12-pdatainstaller 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 legendevil1 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 legendevil1 (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 legendevil1 across your stack and pipelines.

Malicious package

legendevil1PyPI

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

MAL-2026-256

Immediate action

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

pip uninstall legendevil1

What this malware does

Package is designed to download and execute a remote script, which then downloads and runs a malicious executable

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

Campaign: 2025-12-pdatainstaller

Reasons (based on the campaign):

Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
malware

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3188a850ecb974606264f28634afaca67ec2f49c1c759cf590aa39ba19e50452

782226a56313b4a661d694de5f528c5b040f3319b984b7246c339e634e05ab0f

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 legendevil1 (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 legendevil1 across your stack and pipelines.
If you installed it — respond
legendevil1 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 legendevil1 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 legendevil1 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. legendevil1 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

2025-12-pdatainstaller

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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