Which versions of runwifi are malicious?

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

How do I remediate runwifi if I installed it?

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

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

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

Malicious package

runwifiPyPI

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

MAL-2025-3468

Immediate action

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

pip uninstall runwifi

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)

b7ff8ad82dd659963c63b4445217c30c084118079879d2f0137b0e25518be590

1e31c27d94f4aa674279c8c9f3a8a8b6edf1cb710734c76b284a2f20062b0980

83046dbbe0f24ed7ffb9087d78c161e332436c45f2f3f4433606ebb9fd9cc52d

351e9031f2ccfe9287b2a46a2327f1e24d9bd2465f5cbe665317961b0bf4d7a4

6d9080e1d994db74c46850ccae2cec1597e802abc0e54b96c0cbc60fa6885d87

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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