Which versions of btrez-logger are malicious?

The following npm versions of btrez-logger are flagged malicious: 5.0.7, 5.1.0, 5.1.1. Treat any of these as compromised.

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

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

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

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

Search your lockfiles and build artifacts for btrez-logger (3 malicious versions).

Malicious package

btrez-loggernpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

btrez-logger is a confirmed malicious npm package (MAL-2025-41539) that executes malicious code on install (malicious versions 5.0.7, 5.1.0, 5.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in btrez-logger (npm)

MAL-2025-41539

Immediate action

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

npm uninstall btrez-logger

Malicious versions

3 flagged

5.0.75.1.05.1.1

Indicators of compromise (SHA-256)

e51ffe2baa8f93a484be59925816dd38a818ed551c057c27bdb72c5cb9352a69

28ce97aa726310d1370ec812efe6bfcced69e98c3eb0a11a4ed06db2964ebaf9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04474RLUA-2025-05694

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks btrez-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