Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @art-ws published 15 malicious packages. See the full campaign →
Malicious package

@art-ws/config-eslintnpm

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

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

MAL-2025-47372
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @art-ws/config-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
2.0.42.0.5

Indicators of compromise (SHA-256)

21f6bc4896dcd23c1582be957dc11bbb0ab7217304bb96d6986f29408553863b
7b89332826cb57152a8288941846a48e6ecb1d8d979bf641a288f740c34a0b99
793b711cf31c90bd7f9be9fd88a8843374ebc6a1172fad24eeec49f26f98cf52
8e293ce377b0e9dcc25c43f1abba61d9c9ed4f93408dbecb2325d732320eb145

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @art-ws/config-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/config-eslint across your stack and pipelines.

  2. If you installed it — respond

    @art-ws/config-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.

  3. Did it already run?

    If @art-ws/config-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.

  4. How O3 protects you

    O3 blocks @art-ws/config-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/config-eslint on npm has been identified as a malicious package (versions 2.0.4, 2.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x8c4-5f9v-v3ph

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @art-ws/config-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
@art-ws/config-eslint (npm) malicious package — MAL-2025-47372 | O3 Security