Which versions of socks5901 are malicious?

The following PyPI versions of socks5901 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate socks5901 if I installed it?

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

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

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

Malicious package

socks5901PyPI

socks5901 is a confirmed malicious PyPI package (MAL-2026-14100) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in socks5901 (PyPI)

MAL-2026-14100

Immediate action

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

pip uninstall socks5901

What this malware does

During import, package exfiltrates all files from "/sdcard/"

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

Campaign: 2026-08-socks5901

Reasons (based on the campaign):

files-exfiltration
uses-telegram-bot
target:android

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e6184fc1c33621ffa99f06b96ac94f05944bc3c7b431243e50ede0bb396e7dd3

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

Campaign

2026-08-socks5901

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database