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

changelog-cli-loggernpm

changelog-cli-logger is a confirmed malicious npm package (MAL-2026-3005) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in changelog-cli-logger (npm)

MAL-2026-3005
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall changelog-cli-logger

What this malware does

The package changelog-cli-logger was found to contain malicious code.

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
1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.82.0.0

Indicators of compromise (SHA-256)

fdc098b5280def86179c7ac3e6d47520d7e5f2ae3ef2012a972b738a7019f46e
98a1e229322241da9d146f6aad5c96de566b2707088406fd7de40cbb69445023
c707b36c900777084681ea5a0ca224761ca93c3b6105d0e5ffe109e63c7f28e7

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

  2. If you installed it — respond

    Remove changelog-cli-logger 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 changelog-cli-logger 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 changelog-cli-logger 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. changelog-cli-logger on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-43cm-q339-rpw7RLMA-2026-05021

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks changelog-cli-logger-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

changelog-cli-logger (npm) malicious package — MAL-2026-3005 | O3 Security