Which versions of node-loggerx are malicious?

The following npm versions of node-loggerx are flagged malicious: 0.3.0, 0.3.1. Treat any of these as compromised.

How do I remediate node-loggerx if I installed it?

Remove node-loggerx 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 node-loggerx — how do I know if it already compromised me?

If node-loggerx 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 node-loggerx part of a known attack campaign?

Yes — node-loggerx is associated with the GHSA-q4v8-f945-hgp2, RLMA-2025-04610, RLUA-2025-05894 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 node-loggerx 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 node-loggerx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-loggerx across your stack and pipelines.

Malicious package

node-loggerxnpm

node-loggerx is a confirmed malicious npm package (MAL-2025-6366) that executes malicious code on install (malicious versions 0.3.0, 0.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-loggerx (npm)

MAL-2025-6366

Immediate action

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

npm uninstall node-loggerx

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

2 flagged

0.3.00.3.1

Indicators of compromise (SHA-256)

25f40908b2a7b04409b374e0ebaa8c64795147e55c355bdc0c3d3d783d5180e0

1f5e13ecea9440e00a25466155d1a5f3aca6228b16544177167a7e3b9ddfe971

20d9a088e1b9329e9ea64439bd3c989ca2ba33007c010ff634209d2f594592fa

8f27a4f121d3a300dab37f738f255a73b9879a71525904f85649869670bcf812

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 node-loggerx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-loggerx across your stack and pipelines.
If you installed it — respond
Remove node-loggerx 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 node-loggerx 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 node-loggerx 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. node-loggerx on npm has been identified as a malicious package (versions 0.3.0, 0.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q4v8-f945-hgp2RLMA-2025-04610RLUA-2025-05894

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks node-loggerx-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