Which versions of pyfetcher-vaaai are malicious?

The following PyPI versions of pyfetcher-vaaai are flagged malicious: 1.7.2. Treat any of these as compromised.

How do I remediate pyfetcher-vaaai if I installed it?

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

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

Yes — pyfetcher-vaaai is associated with the RLMA-2024-08927, 2024-07-vaaai-netflixchecker, RLUA-2026-00632 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 pyfetcher-vaaai 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 pyfetcher-vaaai (version 1.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyfetcher-vaaai across your stack and pipelines.

Malicious package

pyfetcher-vaaaiPyPI

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

MAL-2024-10116

Immediate action

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

pip uninstall pyfetcher-vaaai

What this malware does

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

Campaign: 2024-07-vaaai-netflixchecker

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

1 flagged

1.7.2

Indicators of compromise (SHA-256)

220074e4fda2b4d6f5d81df632de0f9df081097d5bb37596692893de8880bda4

a47780297e2fb40a55116ed8acd23400d15e72e61b651d7bd1b94265a0299a2f

f237a360d6c502e99989196a60d6a7f7fc66731df01c9412c4d5e1eb00d7d8f9

9eff06e79a85855948c9bad1f00713ac42c6c74bae3469cc9c8d6551b6603ac9

c7ebedea96a0dd6f1e2890aa7d7c182db10ec5157da54079b2e9aeaede341e72

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

Campaign

RLMA-2024-089272024-07-vaaai-netflixcheckerRLUA-2026-00632

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pyfetcher-vaaai-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