Which versions of randomwifi are malicious?

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

How do I remediate randomwifi if I installed it?

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

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

Yes — randomwifi is associated with the RLMA-2025-02527, 2025-03-randomwifi, RLUA-2026-00685 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 randomwifi 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 randomwifi (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 randomwifi across your stack and pipelines.

Malicious package

randomwifiPyPI

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

MAL-2025-3463

Immediate action

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

pip uninstall randomwifi

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)

c09e8bf705840deeb40aba43d53b70d14027f77cddea85388f4127f610786920

b6cfd7d9980a555db2763a3e8b5b162cf73a26a4af7e8de28f3ecea3583c561a

69dd88ab3dd3a84c89517f453703ddfd713ccc663b6641d5cf098e17bcdfe500

9a3af17170f989fe39d826cbdba3b780930fca321ea46d03ccd7a9afb9b791b2

96e9a799c0e749019136e791038a1ac8305f82dd3d9887ebfe47a995b7810b1a

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 randomwifi (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 randomwifi across your stack and pipelines.
If you installed it — respond
randomwifi 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 randomwifi 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 randomwifi 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. randomwifi 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-025272025-03-randomwifiRLUA-2026-00685

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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