Which versions of vramx are malicious?

The following PyPI versions of vramx are flagged malicious: 1.6.2, 1.6.3. Treat any of these as compromised.

How do I remediate vramx if I installed it?

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

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

Yes — vramx is associated with the RLMA-2025-03713, 2025-07-memlib, RLUA-2026-00896 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 vramx 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 vramx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vramx across your stack and pipelines.

Malicious package

vramxPyPI

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

MAL-2025-6614

Immediate action

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

pip uninstall vramx

What this malware does

Installing the package triggers a code that looks like downloading a picture, but in fact downloads and starts an executable with malware. Note that file supplied from the URL differs depending on the presence of the special header

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

Campaign: 2025-07-memlib

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
malware

Malicious versions

2 flagged

1.6.21.6.3

Indicators of compromise (SHA-256)

f7c3b13dd81d9556d87682fcd23b642c8d06e76f69e881687d910d19fa400e4c

cc227cb6fe3c505ae130ee02622905e256e454ca361401abf8cf8f1fab05466d

62a5bfc96a523ea6df6a2539bea5f16b48800c1896ef7fb2df344ed0486e6a49

5d75fb493af32f4d76706c4f6d2390bcb6fc70e8fa9d384e3165aebf27e279f8

2e77789045263235fc9bcd41e477640b1c94855f2c6c21f53d551d0eacb3f3a8

102c0c8e569daf1fc179cf0df9c131db6d78d449f25e584de4a5e2cd662d51ca

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

Campaign

RLMA-2025-037132025-07-memlibRLUA-2026-00896

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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