Dependency Confusion Attack in internallib_v550: Malicious Code Execution
Summary
MAL-2026-16439: Malicious code in internallib_v550 (npm). Affects internallib_v550 versions 1.0.1. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
internallib_v550 is a package published to the public npm registry, designed to resemble an internal private library. It is intended for use in Node.js applications, but its malicious nature poses significant risks. The package's description is simply 'pwn', indicating its harmful intent. This package exploits dependency confusion by masquerading as a legitimate library, leading to potential security breaches in applications that mistakenly use it.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the internallib_v550 package. When the exported function 'command' is invoked, it executes a shell command that spawns a bash process to run 'id', logging 'infected' on the consumer host. This behavior indicates a dependency-confusion attack, where the package is designed to execute harmful commands rather than provide legitimate functionality. The attack does not trigger during installation or import but occurs when the function is explicitly called, making it stealthy and dangerous.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internallib_v550If 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the package entirely. Avoid calling the exported function 'command' if the package is still present in your project.
Conclusion
The internallib_v550 package poses a significant security risk due to its embedded malicious code designed to execute harmful commands. It is crucial to remove this package from your projects and monitor your dependencies for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for internallib_v550 →
FAQ
internallib_v550 is a malicious npm package that mimics an internal library, designed to execute harmful commands when its function is called.
The vulnerability manifests when the exported function 'command' is invoked, leading to the execution of a shell command that can compromise the host system.
If you have internallib_v550 installed, you should uninstall it immediately using 'npm uninstall internallib_v550' and check your project for any references to it.
Yes, Vulert can monitor and alert you for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities without requiring access to the code.
No, there is no patched version of internallib_v550 as it is a malicious package. The best course of action is to remove it from your project.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
