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/db-contextnpm

Advisory published Updated

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

Malicious code in @art-ws/db-context (npm)

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

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.212.0.24

Indicators of compromise (SHA-256)

bb296e15b02ae1bd35dc3ee305d44dc000c3b05057b84bb5409ea0a0ddfb9866
72aeba541e18c7562da7a71bea780fecdb34e6a64f033ee26245d2349ca786df
cb9b4873e315f5a4a01e107dda20ced3c2e726a8215c3f477c90b3f17bcf5b01
8324ec5f0dee4e55e0414d48bdad9a254c95943064106854a5272221d1fd1b2c

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @art-ws/db-context (2 malicious versions).

  2. If you installed it — respond

    @art-ws/db-context 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/db-context was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @art-ws/db-context on npm has been identified as a malicious package (versions 2.0.21, 2.0.24 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hw22-4r5h-554j

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @art-ws/db-context-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/db-context (npm) malicious package — MAL-2025-47374 | O3 Security