Which versions of sccket are malicious?

The following PyPI versions of sccket are flagged malicious: 3.8.5.1. Treat any of these as compromised.

How do I remediate sccket if I installed it?

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

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

Yes — sccket is associated with the RLMA-2025-02533, 2025-03-randomwifi, RLUA-2026-00746 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 sccket 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 sccket (version 3.8.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sccket across your stack and pipelines.

Malicious package

sccketPyPI

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

MAL-2025-3469

Immediate action

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

pip uninstall sccket

What this malware does

Running the module will exfiltrate files from the current directory

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

Campaign: 2025-03-randomwifi

Reasons (based on the campaign):

files-exfiltration
typosquatting

Malicious versions

1 flagged

3.8.5.1

Indicators of compromise (SHA-256)

29a9a863c597f4d01aea243a9cc2ebd5db87885ecc9862fc0fd6f6d939f84ca8

7558cc14dded9c7f64761cd8ed338732146e6b61ddd3b71c968d2e6377a0d98f

5a4f6b8eead6d682b7462da07822a284425fa81c17b9493dd8702ba6a8e5fbb7

9c7237e454f177da0144ef00ff3861b1fe63c349927f9beb8bbe1f929b441790

a1b968038107877a33903b39d4533fc7678966f178aab33176cf738d218b6d43

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

Campaign

RLMA-2025-025332025-03-randomwifiRLUA-2026-00746

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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