Which versions of my-super-lib are malicious?

The following PyPI versions of my-super-lib are flagged malicious: 0.3.0, 0.4.0, 0.6.0, 14.6.0. Treat any of these as compromised.

How do I remediate my-super-lib if I installed it?

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

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

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

Malicious package

my-super-libPyPI

Malicious code in my-super-lib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1434

Immediate action

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

pip uninstall my-super-lib

What this malware does

During import, package decrypts and runs a malicious executable. The executable is hidden in an encoded and xored form in the JSON resource file.

This is a follow up of the campaign 2026-03-fastapi-middleware-cors

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

Campaign: 2026-03-ariadne-federation

Reasons (based on the campaign):

malware
obfuscation
dependency-confusion
typosquatting

Malicious versions

4 flagged

0.3.00.4.00.6.014.6.0

Indicators of compromise (SHA-256)

58a8ef40f042f56d80d455abeb03442516dfd8ed81f462d9da071089ff82f31e

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

Campaign

2026-03-ariadne-federation

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks my-super-lib-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