Which versions of pyfernet are malicious?

The following PyPI versions of pyfernet are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pyfernet if I installed it?

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

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

Yes — pyfernet is associated with the RLMA-2025-03020, 2025-05-fernets, RLUA-2026-00630 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 pyfernet 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 pyfernet (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyfernet across your stack and pipelines.

Malicious package

pyfernetPyPI

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

MAL-2025-5123

Immediate action

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

pip uninstall pyfernet

What this malware does

If imported, the module starts a multi-stage infostealer, exfiltrating browser data as well as crypto wallets, and also attempts to monitor clipboard looking for crypto wallets addresses

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

Campaign: 2025-05-fernets

Reasons (based on the campaign):

infostealer
clipboard-stealing
exfiltration-generic
obfuscation
exfiltration-browser-data
exfiltration-crypto
typosquatting

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ed80ef98612eb3aaad949163f4f0cc751265b3940a964d57baf1153a585d14cb

fdff1f19e5f1ab997df824814e20a0e45bd067a964d72433e069ea9d343d0cf1

5a2f90c0e3c6e46456cd3e319aaaf4a7b53475a554a997a964fdda898e85fcd0

0980354b90f27172271c592fe956b26f0da8bc72c831d8992ca262c4dda1edc5

c395211e960cd02a5539b696480a5c6ea8687457f14c0fdaa34e33a51c9a01e7

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

Campaign

RLMA-2025-030202025-05-fernetsRLUA-2026-00630

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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