Which versions of error-loggerjs are malicious?

The following npm versions of error-loggerjs are flagged malicious: 7.11.7, 7.11.8. Treat any of these as compromised.

How do I remediate error-loggerjs if I installed it?

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

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

Yes — error-loggerjs is associated with the RLMA-2025-04512, RLUA-2025-05781 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 error-loggerjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for error-loggerjs (2 malicious versions).

Malicious package

error-loggerjsnpm

Advisory published Aug 14, 2025Updated Dec 2, 2025

error-loggerjs is a confirmed malicious npm package (MAL-2025-19796) that executes malicious code on install (malicious versions 7.11.7, 7.11.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in error-loggerjs (npm)

MAL-2025-19796

Immediate action

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

npm uninstall error-loggerjs

What this malware does

The package error-loggerjs was found to contain malicious code.

Malicious versions

2 flagged

7.11.77.11.8

Indicators of compromise (SHA-256)

8b6fb2960e0a2a9c17a36a9a467b8a57ae6c593077f5ffb458c6df2881d5d8b9

3ca4b277e70b2a8671df70d8f1416273ae780bb555d36a8cfbf31697ea96caa1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for error-loggerjs (2 malicious versions).
If you installed it — respond
Remove error-loggerjs 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 error-loggerjs 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. error-loggerjs on npm has been identified as a malicious package (versions 7.11.7, 7.11.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04512RLUA-2025-05781

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks error-loggerjs-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