Which versions of @art-ws/eslint are malicious?

The following npm versions of @art-ws/eslint are flagged malicious: 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate @art-ws/eslint if I installed it?

@art-ws/eslint is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @art-ws/eslint — how do I know if it already compromised me?

If @art-ws/eslint 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 @art-ws/eslint part of a known attack campaign?

Yes — @art-ws/eslint is associated with the GHSA-jgxf-mp53-87pv 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 @art-ws/eslint 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 @art-ws/eslint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @art-ws/eslint across your stack and pipelines.

Part of a larger attack: @art-ws published 15 malicious packages. See the full campaign →

Malicious package

@art-ws/eslintnpm

@art-ws/eslint is a confirmed malicious npm package (MAL-2025-47377) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.5, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @art-ws/eslint (npm)

MAL-2025-47377

Immediate action

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

npm uninstall @art-ws/eslint

What this malware does

The package was compromised and malicious code added.

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged

1.0.51.0.6

Indicators of compromise (SHA-256)

5b5534f90d27edf2d3fecc18339bc7049668a5673efb6702a2db17d11747999a

83d069d4a2ec97b0c9568ab092221b10e8ee955429fee08d074bb6ef5f985002

5de914911cc9b33c3fe3a8ac5c3d94bb25479ad7edc0b56483d56fc021b97ca3

558c6bb2311bc73b9de1e1e4f3f9e0b7ccf9229e9afa016b8431ca2912487e36

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @art-ws/eslint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @art-ws/eslint across your stack and pipelines.
If you installed it — respond
@art-ws/eslint is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @art-ws/eslint 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 @art-ws/eslint 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. @art-ws/eslint on npm has been identified as a malicious package (versions 1.0.5, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgxf-mp53-87pv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @art-ws/eslint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database