Which versions of @client-web-next/logger are malicious?

The following npm versions of @client-web-next/logger are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @client-web-next/logger if I installed it?

Remove @client-web-next/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 @client-web-next/logger — how do I know if it already compromised me?

If @client-web-next/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 @client-web-next/logger part of a known attack campaign?

Yes — @client-web-next/logger is associated with the RLMA-2026-10611 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 @client-web-next/logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @client-web-next/logger (version 0.0.1).

Part of a larger attack: @client-web-next published 22 malicious packages. See the full campaign →

Malicious package

@client-web-next/loggernpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@client-web-next/logger is a confirmed malicious npm package (MAL-2026-16504) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @client-web-next/logger (npm)

MAL-2026-16504

Immediate action

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

npm uninstall @client-web-next/logger

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d6df0316200416f80dc34bd15f609abe174c21ce248820054ff23da4ba2352bd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10611

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @client-web-next/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