Which versions of pytrv are malicious?

The following PyPI versions of pytrv are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pytrv if I installed it?

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

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

Yes — pytrv is associated with the RLMA-2024-09082, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00671 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 pytrv 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 pytrv (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytrv across your stack and pipelines.

Malicious package

pytrvPyPI

Malicious code in pytrv (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10144

Immediate action

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

pip uninstall pytrv

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fe65455693843ccf42009ceaa1e37766afa42a50f75c4c0294a33c5694bd9c6a

df63677ff6538dbee9f67de5973f92643eadb48941653d686d3d03112f73d4e7

d2f680e10e34dddd65afc0a09e3bc0c05dfb8cbaa5f02f5f0eb6ece5848498f0

08a7ca0384d43b7c4f543984dff862b11bf60ae83bf7fef385ae0a916f712f3d

2c58d53b4c2c4a38d7e62e1b40e5d8b9317620d75bb9edd5bb24623d3dcc26f7

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

Campaign

RLMA-2024-090822024-08-embeds-RealtekHDAudioManagerRLUA-2026-00671

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pytrv-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