Which versions of fb303-core are malicious?

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

How do I remediate fb303-core if I installed it?

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

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

Yes — fb303-core is associated with the 2025-06-diar-ai-basic 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 fb303-core 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 fb303-core (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 fb303-core across your stack and pipelines.

Malicious package

fb303-corePyPI

Malicious code in fb303-core (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191725

Immediate action

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

pip uninstall fb303-core

What this malware does

Research packages targeting typosquatting and dependency confusions, without really harmful behaviour - just calling home through DNS resolver.

Related to 2025-06-stubsout (using the same remote domain), but without dangerous activity

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-06-diar-ai-basic

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

aea35aa0bab583aa476d8431b9ed750aecde04022a8a918256e6728c69f5e578

9a6664f0567b6f568f8f0bef7c03491fd489eda5cf011851346f4c5e8b2a8aea

cca9d43b5686cf7aa8a40986a3ae4131d7a151fb79e6e2d08d042d4ca9f4ba1d

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 fb303-core (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 fb303-core across your stack and pipelines.
If you installed it — respond
fb303-core 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 fb303-core 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 fb303-core 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. fb303-core 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

2025-06-diar-ai-basic

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks fb303-core-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