rdfxvelanpm
rdfxvela is a confirmed malicious npm package (MAL-2026-13491) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rdfxvela (npm)
What this malware does
cli.js embeds a base64-encoded RSA private key in CONFIG.encodedSSHKey. When the user invokes any rx subcommand (signup/login/list/download/deploy), the CLI writes the decoded key to a temp file at mode 0600 and runs ssh -o StrictHostKeyChecking=no -i <key> [email protected] "<cmd>" against the author's signing server. Every recipient of the tarball receives the same key and can log in as ubuntu on 79.72.65.161. Separately, user-entered passwords are interpolated unescaped into the remote shell command line (bash.../auth.sh signup ${username} ${password}), exposing them in remote process argv and logs. There are no install-time or import-time lifecycle hooks, no reads of installer secrets or environment variables, no exfiltration of installer-owned data, and no fetching or execution of remote code on the installer's machine. The shared credential authorizes access to a host owned by the package author; the blast radius is confined to the author's own infrastructure.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rdfxvela (28 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rdfxvela across your stack and pipelines.
If you installed it — respond
rdfxvela 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 rdfxvela 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 rdfxvela 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks rdfxvela-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.