Which versions of supersafepackage are malicious?

The following PyPI versions of supersafepackage are flagged malicious: 2.0.0, 3.0.0, 3.0.1, 3.0.5, 3.0.6, 4.0.0, 4.0.1, 5.0.0, 6.0.0, 6.0.1. Treat any of these as compromised.

How do I remediate supersafepackage if I installed it?

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

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

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

Malicious package

supersafepackagePyPI

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

MAL-2025-41770

Immediate action

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

pip uninstall supersafepackage

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

10 flagged

2.0.03.0.03.0.13.0.53.0.64.0.04.0.15.0.06.0.06.0.1

Indicators of compromise (SHA-256)

f6709afd6737a8fc0f2e904caf6cb6d52bac0e987d1db631c572351b76840136

e363bbd8e62f9255c8bac406b6190a9dd2f42c103db8dd0824518ef14f363f6f

3b979e1e2520c4f9d07507acc8182830203309adcb9932103a475d3e23e0de3f

4db3e8dcb86b07384aa9fd4286f4f7c8d75994d911844e7a2f419521ef4c5a06

9bfd96a08f3373eb4c871b21b9624939db092b80e4a57d67dd34352b9d5c50de

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 supersafepackage (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging supersafepackage across your stack and pipelines.
If you installed it — respond
supersafepackage 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 supersafepackage 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 supersafepackage 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. supersafepackage on PyPI has been identified as a malicious package (versions 2.0.0, 3.0.0, 3.0.1, 3.0.5, 3.0.6, 4.0.0, 4.0.1, 5.0.0, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04268GENERIC-questionable-pentestRLUA-2026-00789

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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