Which versions of useregent-generator are malicious?

The following PyPI versions of useregent-generator are flagged malicious: 1.6.5. Treat any of these as compromised.

How do I remediate useregent-generator if I installed it?

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

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

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

Malicious package

useregent-generatorPyPI

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

MAL-2024-11741

Immediate action

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

pip uninstall useregent-generator

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

Indicators of compromise (SHA-256)

1dc2a3f3e1dfda0cca42b2a0d5dd9f5f89c9f62f98225049dcc25db6ca079336

86aca124212af00c9576471eba0b3842cdeab589089ccada90890b283400d465

f0c8bbc66c2a8384b2a35340f4e3204351fbeb78d88a11bec270f8e3e52b5636

55e728d0612d4dbdba8f0dbd916f3fdc2f617652af191d024bef18036ce3366c

115547d162414af6a7357adfe733e0e795f3f345b506119ff5e59082324d09bf

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

Campaign

RLMA-2024-112022024-10-fake-usreagentRLUA-2026-00877

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks useregent-generator-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