Malicious Code Injection in mass_ocelot_0xrequest Package

mass_ocelot_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105650: Malicious code in mass_ocelot_0xrequest (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mass_ocelot_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm registry. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise the integrity of applications relying on it.

Vulnerability Detail

The vulnerability originates from the mass_ocelot_0xrequest package being associated with a token reward campaign that exploits npm. The malicious code within this package modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting applications that depend on this package. The ramifications include compromised application integrity, inflated developer reputation scores, and increased security risks.

How To Fix

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

npm uninstall mass_ocelot_0xrequest

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 workaround, you can remove the mass_ocelot_0xrequest package from your project by executing the following command: npm uninstall mass_ocelot_0xrequest. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The mass_ocelot_0xrequest package has been identified as containing malicious code that can compromise applications using it. It is crucial for developers to take immediate action by updating or removing the package to ensure the security of their applications. Monitoring tools like Vulert can assist in identifying such vulnerabilities in real-time.

See every vulnerability recorded for mass_ocelot_0xrequest →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can compromise your application's integrity by introducing malicious code that alters package configurations.

You should immediately update or uninstall the mass_ocelot_0xrequest package to mitigate the risks associated with this vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall mass_ocelot_0xrequest

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