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

log-upgradenpm

Advisory published Updated

log-upgrade is a confirmed malicious npm package (MAL-2026-6849) that executes malicious code on install (malicious version 7.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in log-upgrade (npm)

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

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

1 flagged
7.1.0

Indicators of compromise (SHA-256)

f55c4d43e953e16c7d0325948c789e0fdf1acefaca4b47ceabf199a5288e6f82
00809bf9aae234287af0da8203b4c74e61dbd5908af987582e43c6e13c07b0d8
3c84b1a6c610135d3a4133890c377587f27fb764cb00a04c991a22987a224d32

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for log-upgrade (version 7.1.0).

  2. If you installed it — respond

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

Campaign

GHSA-xf9v-w8wv-g9r4RLMA-2026-05144RLUA-2026-06311

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks log-upgrade-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

log-upgrade (npm) malicious package — MAL-2026-6849 | O3 Security