Which versions of changelog-logger-wrap are malicious?

Every published version of changelog-logger-wrap on npm is considered malicious. Remove the package entirely.

How do I remediate changelog-logger-wrap if I installed it?

Remove changelog-logger-wrap 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.

I already installed changelog-logger-wrap — how do I know if it already compromised me?

If changelog-logger-wrap 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.

Is changelog-logger-wrap part of a known attack campaign?

Yes — changelog-logger-wrap is associated with the GHSA-59ff-98r4-m9mp campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find changelog-logger-wrap across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for changelog-logger-wrap (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging changelog-logger-wrap across your stack and pipelines.

Malicious package

changelog-logger-wrapnpm

Malicious code in changelog-logger-wrap (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1928

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall changelog-logger-wrap

What this malware does

The package changelog-logger-wrap 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

9249189c80ba7b271d8668d501d1f00d34f7dc17cb8f651a2fd5aa65be1ab813

caec1e4b5fc6ded7cff261c7800c1e9753b865564ac6af1674b9450e4c15f577

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for changelog-logger-wrap (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging changelog-logger-wrap across your stack and pipelines.
If you installed it — respond
Remove changelog-logger-wrap 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.
Did it already run?
If changelog-logger-wrap 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.
How O3 protects you
O3 blocks changelog-logger-wrap 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-logger-wrap on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-59ff-98r4-m9mp

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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