Which versions of fernetpy are malicious?

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

How do I remediate fernetpy if I installed it?

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

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

Yes — fernetpy is associated with the RLMA-2025-03010, 2025-05-fernets, RLUA-2026-00321 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 fernetpy 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 fernetpy (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 fernetpy across your stack and pipelines.

Malicious package

fernetpyPyPI

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

MAL-2025-5113

Immediate action

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

pip uninstall fernetpy

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)

e2485adeffcd3ffb56d8c99cecc23d8d508c787ca821faf965736df364b9cc5d

26bc717d266121cbc5725a149e72c0a72e2f8cabb215cf51d37a531aa023d7ab

ccbbcfd921dcefb2809ba41756181682f7a04f1a9f701adcf0c37c9889d87a98

112a124ac1daeb161851b08c066642117c679c43694a17db59424fe617c5d1e2

411b43bcc1df4e0cc272a154d88a8ccf04da0699bcc69179b12d08a74a1581be

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 fernetpy (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 fernetpy across your stack and pipelines.
If you installed it — respond
fernetpy 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 fernetpy 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 fernetpy 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. fernetpy 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-030102025-05-fernetsRLUA-2026-00321

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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