Malicious Code Injection in @art-ws/db-context: A Critical Security Threat
Summary
MAL-2025-47374: Malicious code in @art-ws/db-context (npm). Affects @art-ws/db-context versions 2.0.21 – 2.0.24. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @art-ws/db-context package is an npm library designed for database context management in JavaScript applications. It provides developers with tools to efficiently handle database interactions. However, this package has been compromised, making it susceptible to security threats that can affect applications relying on it.
Vulnerability Detail
The vulnerability stems from the Shai-Hulud NPM worm, which compromised the @art-ws/db-context package by injecting malicious code. This code is designed to steal tokens and credentials from users and publish them to GitHub. Additionally, it can propagate itself to other npm packages owned by the user, leading to widespread security breaches. The affected versions include 2.0.24 and 2.0.21, which are now considered unsafe for use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @art-ws/db-contextIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can remove the @art-ws/db-context package from your project until a secure version is confirmed. You can do this by running: npm uninstall @art-ws/db-context. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @art-ws/db-context package has been compromised, posing significant security risks to applications that utilize it. It is crucial to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for @art-ws/db-context →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials and propagate itself to other npm packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to prevent exploitation.
Versions 2.0.24 and 2.0.21 are known to be compromised. Always check for the latest version and ensure it is secure before using it.
Vulert uses your package-lock.json file to monitor for vulnerabilities in real-time, providing alerts and insights without requiring code access or installation.
