Critical Malicious Code Vulnerability in oj-sp-common-util Package
Summary
MAL-2026-63: Malicious code in oj-sp-common-util (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
Background
The oj-sp-common-util package is a utility library designed for use in Node.js applications, providing various common functionalities to streamline development. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their applications.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the oj-sp-common-util package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall oj-sp-common-util
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 workaround, if you need to maintain functionality that oj-sp-common-util provided, consider using alternative packages that offer similar utilities without the associated risks. Always review the security status of any package before installation.
Conclusion
The oj-sp-common-util package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for oj-sp-common-util →
FAQ
You should immediately uninstall the package using the command 'npm uninstall oj-sp-common-util' and rotate any sensitive information stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
CWE-506 refers to a classification for software that contains embedded malicious code, indicating that the software can perform unauthorized actions.