Which versions of eslint-plugin-consumerweb are malicious?

The following npm versions of eslint-plugin-consumerweb are flagged malicious: 1.10.1, 1.10.2, 1.10.3. Treat any of these as compromised.

How do I remediate eslint-plugin-consumerweb if I installed it?

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

If eslint-plugin-consumerweb was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is eslint-plugin-consumerweb part of a known attack campaign?

Yes — eslint-plugin-consumerweb is associated with the GHSA-7fxc-r56h-xr2j, RLMA-2025-05359, RLUA-2025-05786 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 eslint-plugin-consumerweb across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-plugin-consumerweb (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-consumerweb across your stack and pipelines.

Malicious package

eslint-plugin-consumerwebnpm

eslint-plugin-consumerweb is a confirmed malicious npm package (MAL-2025-47976) that executes malicious code on install (malicious versions 1.10.1, 1.10.2, 1.10.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-consumerweb (npm)

MAL-2025-47976

Immediate action

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

npm uninstall eslint-plugin-consumerweb

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

1.10.11.10.21.10.3

Indicators of compromise (SHA-256)

5f0908b28feb167dcbd08913b9ddf69ed6e3dab2f79a88d0b757e0869acb4e55

c1be24becab5b24acb3424827dbf1a6b1fa5809b9047b328679d938df5c2c410

0f05560e6d61a6a57aa6cc60fac1d2ad7347092c0f2d37e79601d72e7088adae

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-plugin-consumerweb (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-consumerweb across your stack and pipelines.
If you installed it — respond
Remove eslint-plugin-consumerweb 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 eslint-plugin-consumerweb was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks eslint-plugin-consumerweb before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. eslint-plugin-consumerweb on npm has been identified as a malicious package (versions 1.10.1, 1.10.2, 1.10.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7fxc-r56h-xr2jRLMA-2025-05359RLUA-2025-05786

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-plugin-consumerweb-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