What does the libsocks5 malware do?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2023-11-update-information-endpoint Reasons (based on the campaign): - obfuscation - The package overrides the install command in setup.py to execute malicious code during installation. - typosquatting

Which versions of libsocks5 are malicious?

The following PyPI versions of libsocks5 are flagged malicious: 1.1.1, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4. Treat any of these as compromised.

How do I remediate libsocks5 if I installed it?

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

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

Yes — libsocks5 is associated with the RLMA-2024-04108, RLUA-2024-08472, 2023-11-update-information-endpoint, RLUA-2025-06573, RLUA-2026-00471 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 libsocks5 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 libsocks5 (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging libsocks5 across your stack and pipelines.

Malicious package

libsocks5PyPI

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

MAL-2024-5326

Immediate action

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

pip uninstall libsocks5

What this malware does

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

Campaign: 2023-11-update-information-endpoint

Reasons (based on the campaign):

obfuscation
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

6 flagged

1.1.11.7.01.7.11.7.21.7.31.7.4

Indicators of compromise (SHA-256)

09951764d125cccafdedff570d8c1c23f5b758818f2a4ea86b0136a5e96c5906

7b9c6e3863fb099d4f96269a21ae60faeb39f6c45a1829c7d8769feee39a61ae

7abec419c903e1d92e16ac461f7341cf082938f35cb182b8979aab8e36890ef1

f9d745820f944dd4aaf916168db7546fdd4689ac873f85166e92e87329caa3f9

3bc6b0fec4a6b3540f79ae0d408b8ef65f96121f5d7c5a0a9e8e0634870311a1

4b82d3906b35e14e4078a8184b5d95d7d1e622ab655e6618a4601d3547663492

62ebf5035d67a23fcfe010910da67b449bb1a3ea0adc6342fa54f65533597135

95d52f8935641ff1eddd16e3b9a6b96807a7d64453d25f30c3b3f267c7e490f3

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

Campaign

RLMA-2024-04108RLUA-2024-084722023-11-update-information-endpointRLUA-2025-06573RLUA-2026-00471

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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