Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

user-random-agent-userPyPI

Malicious code in user-random-agent-user (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11740
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall user-random-agent-user

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.7.0

Indicators of compromise (SHA-256)

c6d508c48df9a8cdf2fe3c7a607806714dede959392a347e7c9721cd5d450a54
47d7b1e6e7013b8467e73cbc57774d0b1447e36ee40f84bdd1105d1f503381df
593686652ece19b8d2d79006659b8392c347442f9a8403ef1b9f8a8bfa232925
756bff21f4aeaa486c93770227eee7f2fa49feae8122b9ac63b8d298e811c7e9
d15da98f9caad6cf842f5159abd5ae2383d1dc4d5da4ab0f4cf7b001ecd15356

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for user-random-agent-user (version 1.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging user-random-agent-user across your stack and pipelines.

  2. If you installed it — respond

    user-random-agent-user 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.

  3. Did it already run?

    If user-random-agent-user 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.

  4. How O3 protects you

    O3 blocks user-random-agent-user 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. user-random-agent-user on PyPI has been identified as a malicious package (version 1.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-112012024-10-fake-usreagentRLUA-2026-00876

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks user-random-agent-user-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
user-random-agent-user (PyPI) malicious package — MAL-2024-11740 | O3 Security