Critical Malicious Code Vulnerability in internal-company-sdk Package
Summary
MAL-2026-338: Malicious code in internal-company-sdk (npm). Affected versions are not published. 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
The internal-company-sdk is an npm package designed for internal company use, providing various functionalities that streamline development processes. However, it has been compromised, embedding malicious code that poses significant security risks to any system utilizing this package. This vulnerability can lead to unauthorized access and potential data breaches.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the internal-company-sdk package. Any system that has this package installed is considered fully compromised, allowing attackers to gain control over the system. This can result in the exposure of sensitive information, including secrets and keys stored on the affected computer. The malicious code is designed to operate stealthily, making detection and removal challenging.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internal-company-sdkIf 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
There are no effective workarounds to mitigate the risks associated with this vulnerability. The only recommended action is to uninstall the compromised package and secure your system.
Conclusion
The internal-company-sdk package has been compromised with malicious code, posing severe security risks. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.
See every vulnerability recorded for internal-company-sdk →
FAQ
You should uninstall the package immediately and rotate any sensitive information stored on the affected system.
If you have the internal-company-sdk package installed, your system is considered compromised. You can use tools like Vulert to monitor and alert for vulnerabilities.
No, there is currently no patched version available for the internal-company-sdk package.
Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Vulert monitors your package-lock.json file to alert you of open-source vulnerabilities in your software without requiring code access. You can check for vulnerabilities using the Vulert playground.
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.
