Which versions of rei-internal-logger are malicious?

The following npm versions of rei-internal-logger are flagged malicious: 99.9.9, 100.0.0. Treat any of these as compromised.

How do I remediate rei-internal-logger if I installed it?

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

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

Yes — rei-internal-logger is associated with the RLMA-2026-05274, RLUA-2026-06434 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 rei-internal-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rei-internal-logger (2 malicious versions).

Malicious package

rei-internal-loggernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

rei-internal-logger is a confirmed malicious npm package (MAL-2026-7382) that executes malicious code on install (malicious versions 99.9.9, 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rei-internal-logger (npm)

MAL-2026-7382

Immediate action

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

npm uninstall rei-internal-logger

Malicious versions

2 flagged

99.9.9100.0.0

Indicators of compromise (SHA-256)

002e272304c49c08a28ba590bf8bed26a5b718ffca5d165528d01991fb7d5aa3

fdc83093273fff02279459e7422a8ba8bcb1b43335fa99af69808409924748cb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05274RLUA-2026-06434

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rei-internal-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