Which versions of fake-usreagant are malicious?

The following PyPI versions of fake-usreagant are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate fake-usreagant if I installed it?

fake-usreagant is a typosquat — you almost certainly intended a legitimately-named package. Remove fake-usreagant, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed fake-usreagant — how do I know if it already compromised me?

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

Yes — fake-usreagant is associated with the 2024-10-old-fake-usreagant 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 fake-usreagant 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 fake-usreagant (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fake-usreagant across your stack and pipelines.

Malicious package

fake-usreagantPyPI

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

MAL-2024-12270

Immediate action

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

pip uninstall fake-usreagant

What this malware does

Package imitates the legitimate fake-useragent, however it has a few suspicious additions: fake.py L149 calls a function from 'urllib2' module, which contains a code attempting to JSON-deserialize encoded code. This is a pickle executing os.system(id), which of course isn't executed by json.loads, but would be by pickle. Also: action is suspicious, not really malicious, but the package is a clear typosquatting attempt.

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: 2024-10-old-fake-usreagant

Reasons (based on the campaign):

action-hidden-in-lib-usage
clones-real-package
typosquatting
dependency-confusion

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

de00b37f49e2ff19849cb3269e70e2ad85aefca4a3a84f75aa1ad1bffec9cf3d

ef713dc551a4b2eb9b0c94b270f4c214aa90e688076e15bb263b3bb5f3b8484b

5d26cc05453bac24155479cf8ef3bd0bff5a647bdfec50efdec5e27e634361a1

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fake-usreagant (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fake-usreagant across your stack and pipelines.
If you installed it — respond
fake-usreagant is a typosquat — you almost certainly intended a legitimately-named package. Remove fake-usreagant, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If fake-usreagant 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 fake-usreagant 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. fake-usreagant on PyPI has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-10-old-fake-usreagant

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks fake-usreagant-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring