Critical Malicious Code Vulnerability in oj-sp-common-strings Package
Summary
MAL-2026-62: Malicious code in oj-sp-common-strings (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 oj-sp-common-strings package is an npm library designed to provide common string utilities for JavaScript applications. It is widely used in various projects for its simplicity and efficiency in handling string operations. However, this package has been compromised, leading to severe security implications for any application that integrates it.
Vulnerability Detail
The vulnerability originates from the presence of malicious code embedded within the oj-sp-common-strings package. This code can fully compromise any computer running the package, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code that poses a significant threat to system integrity and data security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall oj-sp-common-stringsIf 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 measure, you can prevent the use of the compromised package by removing it from your dependencies and replacing it with an alternative string utility library that is known to be secure.
Conclusion
The oj-sp-common-strings package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to remove 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-strings →
FAQ
You should remove the package immediately and rotate any secrets or keys stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete compromise of the affected system.
While most npm packages are safe, it is crucial to monitor dependencies regularly and use tools like Vulert to stay informed about vulnerabilities.
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.
