Malicious code in rdfxvela (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13491
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5d55d64f24399db1a58a47cf2115a125bdc505d5d9c3bcf0d128e398f2dc6911) 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. ## Source: ghsa-malware (5241f59602a2e4de39cd8c2a2823109c7d7d6e03afd2b906d869a8cfebc8c24d) 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.
- Source published
- 7 Aug 2026 00:06:23 UTC
- Source modified
- 7 Aug 2026 12:35:20 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.