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/http-servernpm

@art-ws/http-server is a confirmed malicious npm package (MAL-2025-47379) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.21, 2.0.24, 2.0.25). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @art-ws/http-server (npm)

MAL-2025-47379
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @art-ws/http-server

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

3 flagged
2.0.212.0.242.0.25

Indicators of compromise (SHA-256)

a32d99dbd1a6a763a936657683bc2f32a37679b532886579d22ea76f50fcfdb3
1148086ae7be1e10c209ad1d5b54d91c8c7c651b11f99c6d01b7f79a84118212
5b6acfc38d83443e6082fb3c838ea61bf2b51a25fe92ad8c4a6c2424396461f6
88a87a9282007fc803fd523f607d3fb49b1889b4f0fd83ac519b1f9c004cc5cb

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/http-server (3 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/http-server across your stack and pipelines.

  2. If you installed it — respond

    @art-ws/http-server 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/http-server 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/http-server 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/http-server on npm has been identified as a malicious package (versions 2.0.21, 2.0.24, 2.0.25 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m3m6-cg8g-rhvf

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@art-ws/http-server (npm) malicious package — MAL-2025-47379 | O3 Security