Which versions of usvr-agent are malicious?

The following PyPI versions of usvr-agent are flagged malicious: 0.1.0, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate usvr-agent if I installed it?

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

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

Yes — usvr-agent is associated with the RLMA-2025-01253, GENERIC-standard-pypi-install-pentest, RLUA-2026-00878, RLUA-2026-01689 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 usvr-agent 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 usvr-agent (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging usvr-agent across your stack and pipelines.

Malicious package

usvr-agentPyPI

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

MAL-2025-2008

Immediate action

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

pip uninstall usvr-agent

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.1.00.2.00.3.0

Indicators of compromise (SHA-256)

783e7c855dc7ca39f952e085878b2d8f6672afd6174ef7883163346fde2da810

7a3eac081596280531048d1ddd913b8c2f71c1ba50ab26ee062caa484ae0f4fe

1405e2750a6a5af336cf7ff5a520f14cc72102bac8781cb4540a3e464296359f

001629f2306b8aa194cea60e8546ba1cdd5f17ba30a5b416bbd55d169fd7b23a

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

Campaign

RLMA-2025-01253GENERIC-standard-pypi-install-pentestRLUA-2026-00878RLUA-2026-01689

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks usvr-agent-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