Critical Malicious Code Vulnerability in oj-sp-about-page Package

oj-sp-about-page Updated 06 Jan 2026

Summary

06/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-60: Malicious code in oj-sp-about-page (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-about-page package is an npm library designed to provide specific functionalities related to displaying information about a project or application. It is commonly used in web development to enhance user interfaces. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The oj-sp-about-page package contains embedded malicious code that can fully compromise any computer on which it is installed or running. This vulnerability originates from a malicious actor who has injected harmful code into the package. The ramifications of this vulnerability are severe, as it allows unauthorized access to sensitive information, including secrets and keys stored on the affected system. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall oj-sp-about-page

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, users should rotate all secrets and keys stored on the compromised system from a different, secure computer. This action is necessary to mitigate the risk of unauthorized access.

Conclusion

The oj-sp-about-page package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for oj-sp-about-page →

Share this vulnerability

FAQ

The oj-sp-about-page package is an npm library used for displaying project information in web applications.

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information.

Immediately remove the oj-sp-about-page package and rotate any sensitive information stored on your system.

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

Not necessarily. While removing the package is essential, there may still be residual malicious software that needs to be addressed.

How To Fix

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

npm uninstall oj-sp-about-page

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