Which versions of pyfetcher are malicious?

The following PyPI versions of pyfetcher are flagged malicious: 1.7.2, 1.7.3, 1.7.4, 1.7.5. Treat any of these as compromised.

How do I remediate pyfetcher if I installed it?

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

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

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

Malicious package

pyfetcherPyPI

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

MAL-2024-10115

Immediate action

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

pip uninstall pyfetcher

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

4 flagged

1.7.21.7.31.7.41.7.5

Indicators of compromise (SHA-256)

41c7d201360945bb1164c3a1701238ea37151b3f78bc0965137b2309dfa2639d

10c2ff4313c78f3d53898a30c36069c0e576a7e40db72f8119cbda67ee7f318b

4a689a2d20313b4d2681d50def7abed6ad72462be076e35056a6098556b1a246

6b2edcb5b83d97d4753b45ac26cb8439bfd90a8a2136115fced110ed4b3fde03

415787d837498a7de798a17ef66542f7619c681b213def171d5655d6686f3f1d

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

Campaign

RLMA-2024-089262024-07-vaaai-netflixcheckerRLUA-2026-00631

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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