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

The following npm versions of @art-ws/openapi are flagged malicious: 0.1.9, 0.1.11, 0.1.12. Treat any of these as compromised.

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

@art-ws/openapi 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/openapi — how do I know if it already compromised me?

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

Yes — @art-ws/openapi is associated with the GHSA-v5cf-4rx8-2hm4 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/openapi 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/openapi (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/openapi across your stack and pipelines.

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

Malicious package

@art-ws/openapinpm

@art-ws/openapi is a confirmed malicious npm package (MAL-2025-47380) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.9, 0.1.11, 0.1.12). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2025-47380

Immediate action

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

npm uninstall @art-ws/openapi

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

0.1.90.1.110.1.12

Indicators of compromise (SHA-256)

f3a0ad3b1fc79869257d7f1273c81658ddd9f2d965d6a90ede8a6a56f0bcec03

95bf1ca6cf44627c0e79bccad94ab171021ece601814ac65cc70d055d925a3f0

4476910e2977cc0e809f25558b95b3f0bfed12694c1086cf3a005cd977bd8c07

0d38eee79a6f7393116b943287f6094f9a87956e79af9d2a4da0be4213042d49

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/openapi (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/openapi across your stack and pipelines.
If you installed it — respond
@art-ws/openapi 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/openapi 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/openapi 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/openapi on npm has been identified as a malicious package (versions 0.1.9, 0.1.11, 0.1.12 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v5cf-4rx8-2hm4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @art-ws/openapi-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