Critical Malicious Code Vulnerability in oce-collaborate Package

oce-collaborate Updated 23 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-419: Malicious code in oce-collaborate (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-collaborate package is a Node.js library designed for collaborative functionalities in applications. It allows developers to integrate real-time collaboration features into their software. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the oce-collaborate package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of this code has been confirmed by multiple security sources, indicating that systems running this package should be considered fully compromised.

How To Fix

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

npm uninstall oce-collaborate

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 temporary measure, you can isolate the affected application from the network to prevent further compromise while you work on removing the package. Additionally, rotate all secrets and keys stored on the compromised system from a secure, unaffected machine.

Conclusion

The discovery of malicious code within the oce-collaborate package poses a serious threat to any systems utilizing it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for oce-collaborate →

Share this vulnerability

FAQ

The oce-collaborate package is a Node.js library that enables real-time collaboration features in applications.

If you have the oce-collaborate package installed, your system is likely affected. You can use tools like Vulert to monitor and alert for vulnerabilities.

Immediately rotate all secrets and keys from a secure machine to prevent unauthorized access.

Yes, you can use Vulert, which monitors vulnerabilities using just the package-lock.json file. You can check your application at the Vulert playground without signing up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

How To Fix

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

npm uninstall oce-collaborate

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