Which versions of wacve-utils are malicious?

The following PyPI versions of wacve-utils are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate wacve-utils if I installed it?

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

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

Yes — wacve-utils is associated with the 2026-08-wacve-utils 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 wacve-utils 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 wacve-utils (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wacve-utils across your stack and pipelines.

Malicious package

wacve-utilsPyPI

wacve-utils is a confirmed malicious PyPI package (MAL-2026-11428) that steals credentials and exfiltrates sensitive data (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wacve-utils (PyPI)

MAL-2026-11428

Immediate action

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

pip uninstall wacve-utils

What this malware does

The package contains encrypted code with infostealers targeting Linux and Android (execution under Termux). The encrypted code collects files, browsers data, text messages and exfiltrates them to a Telegram channel.

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

Campaign: 2026-08-wacve-utils

Reasons (based on the campaign):

files-exfiltration
exfiltration-browser-data
uses-telegram-bot
obfuscation
Downloads and executes a remote malicious script.
infostealer

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

de96a68d25555c9ee1792a22b84307ba3bc68d1e012bd841454dc775986260cb

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

Campaign

2026-08-wacve-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks wacve-utils-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