Which versions of stubsoutagn are malicious?

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

How do I remediate stubsoutagn if I installed it?

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

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

Yes — stubsoutagn 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 stubsoutagn 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 stubsoutagn (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stubsoutagn across your stack and pipelines.

Malicious package

stubsoutagnPyPI

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

MAL-2025-191880

Immediate action

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

pip uninstall stubsoutagn

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8b4ebcdac8a5c710bd10f1545c4fcd1481a4d88eb5431a3a8bae03efabd1212b

1d6fba8f0ef8a9e8c54dd8fd281d9202994fc306f4bb614f6cf3ace71fff6164

bd7d3019221dcb623b202c78854daa3faf21d00d08ef22da1f29921b5c8b3c08

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 stubsoutagn (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stubsoutagn across your stack and pipelines.
If you installed it — respond
stubsoutagn 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 stubsoutagn 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 stubsoutagn 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. stubsoutagn on PyPI has been identified as a malicious package (version 0.0.1 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 stubsoutagn-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