What does the fefeefrrg malware do?

Installing the package starts an infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2023-12-fefeefrrg Reasons (based on the campaign): - infostealer - The package overrides the install command in setup.py to execute malicious code during installation. - exfiltration-generic - exfiltration-browser-data - The package contains code to detect if it is running in a sandbox environment.

Which versions of fefeefrrg are malicious?

The following PyPI versions of fefeefrrg are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate fefeefrrg if I installed it?

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

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

Yes — fefeefrrg is associated with the RLMA-2024-03915, RLUA-2024-08271, 2023-12-fefeefrrg, RLUA-2026-00319 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 fefeefrrg 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 fefeefrrg (version 1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fefeefrrg across your stack and pipelines.

Malicious package

fefeefrrgPyPI

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

MAL-2024-5135

Immediate action

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

pip uninstall fefeefrrg

What this malware does

Installing the package starts an infostealer

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

Campaign: 2023-12-fefeefrrg

Reasons (based on the campaign):

infostealer
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-generic
exfiltration-browser-data
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

476d201700857807312e04f094e863d61d7c51ef63c1edd56dbd4862f8c241e7

4631f383d7ad30b59e92dad606c6c32efc4123bed5f450dbffe291761c1c93f9

1881cf262285d7badb09b1dbbc35f309683aac98b03c2bf657900ef9827528d5

3aa8b4ce86737760d29f2bf87c18d7c195bf3c26d83205d1c9972216c0149146

5beaf4b1d416854b73dc3e35a815a42926342dde4d8f09fbf974fad1f9fe8e6f

e9cd3917ceece98595fe4b4d417e70143e6bb349265055a7148d7f866bb0dcf8

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

Campaign

RLMA-2024-03915RLUA-2024-082712023-12-fefeefrrgRLUA-2026-00319

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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