Critical Malicious Code Vulnerability in oj-sp-common Package

oj-sp-common Updated 06 Jan 2026

Summary

06/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-61: Malicious code in oj-sp-common (npm). Affected versions are not published. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The oj-sp-common package is an npm library designed for use in JavaScript applications, providing common functionalities and utilities for developers. 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 projects.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the oj-sp-common package. This code can grant unauthorized access to an attacker, allowing them to control the affected system fully. As a result, any secrets or sensitive information stored on the compromised machine may be exposed. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful.

How To Fix

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

npm uninstall oj-sp-common

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package and securing the system.

Conclusion

The oj-sp-common package has been identified as containing malicious code that compromises system security. 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 →

Share this vulnerability

FAQ

oj-sp-common is an npm package that provides common functionalities for JavaScript applications.

The malicious code can grant attackers full control over your system, potentially exposing sensitive information.

You should remove the oj-sp-common package immediately and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Vulert is a tool that monitors open-source vulnerabilities using just the package-lock.json file, providing real-time alerts for any issues.

How To Fix

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

npm uninstall oj-sp-common

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