Which versions of fake-usreagent are malicious?

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

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

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

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

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

Malicious package

fake-usreagentPyPI

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

MAL-2024-11590

Immediate action

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

pip uninstall fake-usreagent

What this malware does

Inside the library there is a part running code hidden in the attached image, which then exfiltrate user-provided data, downloads and install next stage code, exfiltrate TXT files and finally installs infostealers - Lumma and a custom one. Arround L110

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

Campaign: 2024-10-fake-usreagent

Reasons (based on the campaign):

infostealer
files-exfiltration
clipboard-stealing
obfuscation
clones-real-package
action-hidden-in-lib-usage

Malicious versions

1 flagged

1.6.3

Indicators of compromise (SHA-256)

89b2ea42dc2e9e23895b1c550d87a319a2e3e1c2291a561a5c73aaeab74dfa0c

932976747ede94d7f0707301e4cd3b7666731550f564ab241ec09365bfde48af

f4baefb66829fd54eeb9a557917c302ba8588059ca8483d1a56b06518d7638d4

0a487ff78685ca0ec19a6d5ddde52fec433b58697fa4ffc7f5725defaa04edd9

26113774eca9ca5b5b740516146c775c18f0881cc652e397f9f1eeef5603d259

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

Campaign

RLMA-2024-110412024-10-fake-usreagentRLUA-2026-00311

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks fake-usreagent-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