NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

jfrog-npm-actions-examplenpm

Advisory published Updated

jfrog-npm-actions-example is a confirmed malicious npm package (MAL-2025-49014) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jfrog-npm-actions-example (npm)

MAL-2025-49014
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall jfrog-npm-actions-example

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.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

a600f48287c23fcb6db85ed0ed084de6ce12d7d3fab99e327ec306c6a84ea7f0
ad078ca4de541085260ea9b4b8ba08105215c75bc0e17bfa2fa99b0172b40344
0f4a056c4be2308777989801550e3833f52b9717f0b9945be3c96d70e1a16c92

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for jfrog-npm-actions-example (version 99.0.0).

  2. If you installed it — respond

    jfrog-npm-actions-example 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 jfrog-npm-actions-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. jfrog-npm-actions-example on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v88p-3w5x-p4g9RLMA-2025-05818

References

Credits

  • ReversingLabs · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
jfrog-npm-actions-example (npm) malicious package — MAL-2025-49014 | O3 Security