Which versions of soopsocks are malicious?

The following PyPI versions of soopsocks are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7. Treat any of these as compromised.

How do I remediate soopsocks if I installed it?

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

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

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

Malicious package

soopsocksPyPI

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

MAL-2025-191872

Immediate action

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

pip uninstall soopsocks

What this malware does

The package promise creating a SOCKS proxy and report the server to a Discord webhook. And indeed appears to do so, but the attached autorun service seems to be a malware

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

Campaign: 2025-09-soopsocks

Reasons (based on the campaign):

malware

Malicious versions

12 flagged

0.1.00.1.10.1.20.1.30.2.00.2.10.2.20.2.30.2.40.2.50.2.60.2.7

Indicators of compromise (SHA-256)

6b1d078aff71031e0681d4377e92d0e9d398f3f18d1fc92ab6f97f94a93697d5

adcaa2cfcfa52c7c1ed664a9389ba0bd0ddd2716ea4c475b22bcd2f62bc1ab95

ca432b15dd310c0563790ddbffb84582f20b388625f6860669a89d0522f0b4f1

18dba171f7b25bab5d0a24d26b02d0a38002ec4abe48279f824b4cfc8ac4703c

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 soopsocks (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soopsocks across your stack and pipelines.
If you installed it — respond
soopsocks 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 soopsocks 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 soopsocks 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. soopsocks on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.2.0, 0.2.1, 0.2.2, 0.2.3, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-09-soopsocks

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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