Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

rdfxvela-buildnpm

rdfxvela-build is a confirmed malicious npm package (MAL-2026-13492) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rdfxvela-build (npm)

MAL-2026-13492
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rdfxvela-build

What this malware does

The package contains 4 files and no static or traced findings indicate credential access, network exfiltration, install-time code fetch and execution, silent-relay of caller data, persistence, or other installer-side harmful behavior. No hardcoded attacker endpoints, obfuscated payloads, lifecycle-hook droppers, or credential-store reads are present in the analyzed contents.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

a2d221857ec2b20bcd287d947f2adff2e99f9ab8442e5375ca98fb83e2d86d0a
ef19b46ba2f8a9d7a30bedb44d2e45903d5e4e905d736b5ce5c20cbb0b77be12

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rdfxvela-build (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rdfxvela-build across your stack and pipelines.

  2. If you installed it — respond

    rdfxvela-build 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.

  3. Did it already run?

    If rdfxvela-build 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.

  4. How O3 protects you

    O3 blocks rdfxvela-build 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. rdfxvela-build on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jw4p-5x7w-fcm4IN-MAL-2026-016937

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rdfxvela-build-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

rdfxvela-build (npm) malicious package — MAL-2026-13492 | O3 Security