Which versions of stubsout are malicious?

The following PyPI versions of stubsout are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate stubsout if I installed it?

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

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

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

Malicious package

stubsoutPyPI

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

MAL-2025-191879

Immediate action

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

pip uninstall stubsout

What this malware does

While described as telemetry, importing the package attempts to send out some basic info as well as quite sensitive environmental variables.

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

Campaign: 2025-06-stubsout

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.
exfiltration-env-variables

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

1fedd64d9650a1fb76e6b6e504ee96e4dd2885025813fecf77888d33abc15c72

288961ef642901bbbd1ecf1fee45702985e9691d3f2fdc95f5990a197df2782b

e9dcfff8a0bc41778581a79e2d0be0abe6271b868491b36eb1bc5affc28b395b

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

Campaign

2025-06-stubsout

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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