Which versions of antibyfron are malicious?

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

How do I remediate antibyfron if I installed it?

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

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

Yes — antibyfron is associated with the RLMA-2024-07817, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00069 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 antibyfron 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 antibyfron (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 antibyfron across your stack and pipelines.

Malicious package

antibyfronPyPI

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

MAL-2024-9940

Immediate action

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

pip uninstall antibyfron

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

121b8cf760d7229e73c8cb5f6dfd7617088cb7abbaf9012664df35031bf3634e

6fc9ffd90a21e6217a33fbf5b0de7b061e5134c919d88d7fcb0a5bb50c076b8b

b18b332b0269a1ac32574b6676f3c4a5d85c8bc7d64519987a8ad8d740038331

859447398b4176794849892ea501361098e1f1ff30c946fa399136cad80a5bda

98751de354f1e493bca4ea7a478a7349642d09f90d03690885f8ff661201e4ab

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 antibyfron (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 antibyfron across your stack and pipelines.
If you installed it — respond
antibyfron 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 antibyfron 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 antibyfron 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. antibyfron 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-2024-078172024-08-embeds-RealtekHDAudioManagerRLUA-2026-00069

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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