Which versions of @1nderman/betterconsole are malicious?

The following npm versions of @1nderman/betterconsole are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @1nderman/betterconsole if I installed it?

Remove @1nderman/betterconsole 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 @1nderman/betterconsole — how do I know if it already compromised me?

If @1nderman/betterconsole 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 @1nderman/betterconsole part of a known attack campaign?

Yes — @1nderman/betterconsole is associated with the RLMA-2025-04827, RLUA-2026-05776 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 @1nderman/betterconsole across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @1nderman/betterconsole (version 1.0.0).

Malicious package

@1nderman/betterconsolenpm

Advisory published Sep 26, 2025Updated Sep 1, 2026

@1nderman/betterconsole is a confirmed malicious npm package (MAL-2025-47606) 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 @1nderman/betterconsole (npm)

MAL-2025-47606

Immediate action

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

npm uninstall @1nderman/betterconsole

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3c4a67be69e66f77635a3de3f7f6fa1a07762152660c0c6a00c702fa1a33a6c1

946888fd59c73e1e5d0ed42118dd4ecf92c5996bea260b7b47918bad58cc96e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @1nderman/betterconsole (version 1.0.0).
If you installed it — respond
Remove @1nderman/betterconsole 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 @1nderman/betterconsole 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. @1nderman/betterconsole 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-04827RLUA-2026-05776

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @1nderman/betterconsole-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