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

@ra-ide/udt-frontendnpm

Malicious code in @ra-ide/udt-frontend (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190598
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ra-ide/udt-frontend

What this malware does

The package @ra-ide/udt-frontend was found to contain malicious code.

The OpenSSF Package Analysis project identified '@ra-ide/udt-frontend' @ 141.3.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
141.3.1

Indicators of compromise (SHA-256)

06a45948acd3329d36110e3003adc89e9ce0166c9c468a10c66fca181c535b3e
43e7622a4fb5f78043c8f52ad78fb036d26fa8ae041f8d2d21f82d4620894e14

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove @ra-ide/udt-frontend from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @ra-ide/udt-frontend 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 @ra-ide/udt-frontend 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. @ra-ide/udt-frontend on npm has been identified as a malicious package (version 141.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @ra-ide/udt-frontend-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring