Which versions of runningwifi are malicious?

The following PyPI versions of runningwifi are flagged malicious: 1. Treat any of these as compromised.

How do I remediate runningwifi if I installed it?

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

If runningwifi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is runningwifi part of a known attack campaign?

Yes — runningwifi is associated with the RLMA-2025-02531, 2025-03-randomwifi, RLUA-2026-00738 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 runningwifi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for runningwifi (version 1).

Malicious package

runningwifiPyPI

Advisory published Mar 31, 2025Updated Mar 19, 2026

runningwifi is a confirmed malicious PyPI package (MAL-2025-3467) that steals credentials and exfiltrates sensitive data (malicious version 1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in runningwifi (PyPI)

MAL-2025-3467

Immediate action

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

pip uninstall runningwifi

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

Indicators of compromise (SHA-256)

4f80cc04d5148c8bb847b353db498e9699194fa3b6ea407208f168466b10ad3d

944f3e021c5f3890a80443990cb125e02d54c8ec03ecda6e2042f76fecf9aa37

7c510d8dbbc3448272c337960c786b9b9731fe97773a4bfd48844527c7e6bed6

610d37a3ec31d2eda047d1898e65cc1352a33f8544920e6b5f6563380db3b4e2

6e2abe3ff9b272b177b9b8a7566ca07f68ff6ddb09ea88176e132ba6879124ad

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for runningwifi (version 1).
If you installed it — respond
runningwifi 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 runningwifi was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. runningwifi on PyPI has been identified as a malicious package (version 1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025312025-03-randomwifiRLUA-2026-00738

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database