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

ufo-rocks2npm

ufo-rocks2 is a confirmed malicious npm package (MAL-2024-3253) that executes malicious code on install (malicious versions 0.0.1-security, 0.99.99, 1.99.99…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ufo-rocks2 (npm)

MAL-2024-3253
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ufo-rocks2

What this malware does

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

10 flagged
0.0.1-security0.99.991.99.992.99.993.84.13.84.23.99.994.0.04.99.995.99.99

Indicators of compromise (SHA-256)

3bef4922e3abe5e4aa856296c6a8676dbe49964f28b5eb525eefec31dabeb1bd
39e5a4cb93591c8afd228d1b8a58876110845dc9b9873b3e3c5949f5951d624b
3374b9d8ce913176fed7916c9adf5e5239b09aed801473ef2363bdf190f1c8f6
68373676bdd9f596c9b3c7ee86bc776166b1edfe0d990b5dc9ac97915757a439
ebf92c3121dbd12b02e7494bb809e3fcc152d65edd985f834d5df0f105b8facb
7c8dd857b92b012752686a03ffe42bc95071d581356fa13684b81ea960ddf3cd

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 ufo-rocks2 (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ufo-rocks2 across your stack and pipelines.

  2. If you installed it — respond

    Remove ufo-rocks2 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 ufo-rocks2 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 ufo-rocks2 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. ufo-rocks2 on npm has been identified as a malicious package (versions 0.0.1-security, 0.99.99, 1.99.99, 2.99.99, 3.84.1, 3.84.2, 3.99.99, 4.0.0, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-02017RLUA-2024-07493GHSA-6w67-3mx2-m25rRLUA-2026-01630

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks ufo-rocks2-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.

Explore

ufo-rocks2 (npm) malicious package — MAL-2024-3253 | O3 Security