Which versions of logger-extjs are malicious?

The following npm versions of logger-extjs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate logger-extjs if I installed it?

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

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

Yes — logger-extjs is associated with the RLMA-2025-04590, RLUA-2025-05865 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 logger-extjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for logger-extjs (version 1.0.0).

Malicious package

logger-extjsnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

logger-extjs is a confirmed malicious npm package (MAL-2025-41582) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in logger-extjs (npm)

MAL-2025-41582

Immediate action

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

npm uninstall logger-extjs

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4b2a9cdae59fd841e34e4981a1070d69fb9872e8fa924cc31de8f41f0568224a

a3be990bdde417ff50a7b7b18d1df6971c2d5dc4e12518cc58727e19e86311e0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04590RLUA-2025-05865

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks logger-extjs-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