Which versions of python-socket-test are malicious?

The following PyPI versions of python-socket-test are flagged malicious: 1.0.0, 1.0.1, 1.1.1, 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate python-socket-test if I installed it?

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

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

Yes — python-socket-test is associated with the RLMA-2025-02524, 2025-03-python-socket-test, RLUA-2026-00668 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 python-socket-test 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 python-socket-test (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-socket-test across your stack and pipelines.

Malicious package

python-socket-testPyPI

Malicious code in python-socket-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3460

Immediate action

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

pip uninstall python-socket-test

What this malware does

Importing the package starts a script that takes commands from remote server and executes locally

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

Campaign: 2025-03-python-socket-test

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

5 flagged

1.0.01.0.11.1.12.0.02.0.1

Indicators of compromise (SHA-256)

382f73d1e1afdcb53f0f53d1971a55c246aeab8a4b44cb4bd2e8ad450aac24e4

ebda3713b5dc5450e5ab29810baa209491367514409022f5514a592dd2aa43b3

93a8d30e631680bace9b05db1ac189cbcc472895fcfb1db40f4df52f301a6599

84b55a44b9131e861d0ebe1884bed3f6ec52a705ccb96b8a3861e1a50a1fb8d0

503a73cf105cfe27c48a3bbfce49f33a4ec01fa39ff27d6ebeeebbbd6f3526ba

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

Campaign

RLMA-2025-025242025-03-python-socket-testRLUA-2026-00668

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks python-socket-test-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