Malicious Code Injection in @art-ws/di-node: A Critical Security Threat

@art-ws/di-node Updated 02 Oct 2025

Summary

16/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47376: Malicious code in @art-ws/di-node (npm). Affects @art-ws/di-node versions 2.0.13. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @art-ws/di-node package is a Node.js library designed for dependency injection, facilitating the management of dependencies in JavaScript applications. It is widely used for its simplicity and effectiveness in structuring code. However, this package has recently been compromised, leading to the introduction of malicious code that poses significant security risks to users.

Vulnerability Detail

The vulnerability stems from a compromise of the @art-ws/di-node package, which was infiltrated by the Shai-Hulud NPM worm. This malicious payload is designed to steal sensitive tokens and credentials from users, subsequently publishing this information to GitHub. Furthermore, it propagates itself to other NPM packages owned by the affected users, amplifying the threat and potentially compromising multiple applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @art-ws/di-node

If 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, users can remove the affected package from their project until a secure version is confirmed. This can be done using the command: npm uninstall @art-ws/di-node. Additionally, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The @art-ws/di-node package has been compromised, introducing a serious security vulnerability that can lead to data theft and unauthorized access. Users are urged to update to the latest patched version and consider using tools like Vulert to monitor their applications for vulnerabilities. Taking proactive measures is essential to safeguard your applications.

See every vulnerability recorded for @art-ws/di-node →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive information such as tokens and credentials, which can lead to unauthorized access to user accounts and data.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you suspect that your application has been compromised, immediately revoke any exposed tokens or credentials and update the affected package to the patched version.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to the latest secure versions.

Ignoring this vulnerability can lead to significant security breaches, including data theft, unauthorized access to systems, and potential propagation of the malicious code to other projects.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @art-ws/di-node

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback