Critical Malicious Code Vulnerability in oce-components Package

oce-components Updated 23 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-420: Malicious code in oce-components (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The oce-components package is a library used in Node.js applications, primarily for enhancing functionality and providing reusable components. It is widely utilized in various projects due to its ease of integration and extensive features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the oce-components package. This code can 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 has been confirmed by security sources, indicating that systems running this package should be considered fully compromised. The implications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall oce-components

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, you can temporarily disable the functionalities that rely on the oce-components package until it is removed or updated. Additionally, ensure that no sensitive operations are performed on the compromised system until the issue is resolved.

Conclusion

The discovery of malicious code within the oce-components package poses a serious threat to any system using it. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for oce-components →

Share this vulnerability

FAQ

The oce-components package is a Node.js library used for building applications with reusable components.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

Immediately remove the oce-components package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is crucial to assess the system for any lingering threats.

How To Fix

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

npm uninstall oce-components

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