Which versions of xp-node-logger are malicious?

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

How do I remediate xp-node-logger if I installed it?

Remove xp-node-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.

I already installed xp-node-logger — how do I know if it already compromised me?

If xp-node-logger 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.

Is xp-node-logger part of a known attack campaign?

Yes — xp-node-logger is associated with the GHSA-m6qc-p4mr-59vf 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 xp-node-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xp-node-logger (all published versions).

Malicious package

xp-node-loggernpm

Advisory published Jul 30, 2026Updated Jul 31, 2026

xp-node-logger is a confirmed malicious npm package (MAL-2026-11411) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xp-node-logger (npm)

MAL-2026-11411

Immediate action

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

npm uninstall xp-node-logger

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

all versions

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

Indicators of compromise (SHA-256)

dacb3f21efc94ccf0bbcabc232b84f156d79b073feaf3e5bbfa40bbf998ba1d0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xp-node-logger (all published versions).
If you installed it — respond
Remove xp-node-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.
Did it already run?
If xp-node-logger 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. xp-node-logger 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-m6qc-p4mr-59vf

References

github.com

Detect & block this

O3 blocks xp-node-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database