Which versions of whatsfly_labfox are malicious?

The following PyPI versions of whatsfly_labfox are flagged malicious: 0.2.0, 0.2.1. Treat any of these as compromised.

How do I remediate whatsfly_labfox if I installed it?

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

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

Yes — whatsfly_labfox is associated with the IN-MAL-2026-004517, IN-MAL-2026-004515, IN-MAL-2026-004516, IN-MAL-2026-004518 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 whatsfly_labfox 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 whatsfly_labfox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whatsfly_labfox across your stack and pipelines.

Malicious package

whatsfly_labfoxPyPI

Malicious code in whatsfly-labfox (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4776

Immediate action

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

pip uninstall whatsfly_labfox

What this malware does

On import whatsfly, whatsfly/__init__.py invokes ensureUsableBinaries() from whatsfly/dependencies/builder.py, which downloads a native binary (.so/.dll/.dylib) from the GitHub Actions artifacts API for Labfox/whatsfly, unzips it under whatsfly/dependencies/whatsmeow/, and whatsmeow.py loads it directly via ctypes.CDLL(...). The download is authenticated with a fine-grained GitHub Personal Access Token (github_pat_11AZ7BYQI05SxpWYyU3Ctr_e2PlN...) reconstructed at runtime from a per-character list in whatsfly/dependencies/github_actions_download.py:7 — a deliberate obfuscation pattern used to evade GitHub's automated secret scanning. Two installer-impacting consequences follow: (1) every installer extracts the same live GitHub PAT and can use it against the author's GitHub account and the Labfox/whatsfly repository (credential redistribution to third parties); (2) the fetched artifact is a GitHub Actions artifact (mutable, 90-day TTL) pinned only by the loose string version="v20" with no hash or signature verification — anyone holding the PAT (including any installer of this package) can replace the artifact and achieve remote code execution on every subsequent importer via the ctypes load.

Malicious versions

2 flagged

0.2.00.2.1

Indicators of compromise (SHA-256)

44d4a24d293f810bd11587936b79a835fb0671b7af961328f836d57c7b0c4514

68fe57da48ce63ec7cec5176168ccdfbe05e8b6f83a83c39a0440289141ee2d1

c63e3f4776abe00db50f3d7e34bea3ed308a52b6e0c44872692b0dce50290d1f

f6aa24abde03297259d087a25b56eaa29010b3d2857599bbe9fbe0b60af92959

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

Campaign

IN-MAL-2026-004517IN-MAL-2026-004515IN-MAL-2026-004516IN-MAL-2026-004518

References

Credits

Amazon Inspector · finder

Detect & block this

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