Malicious Code in institutional_ocelot_0xrequest: A Threat to npm Packages

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104260: Malicious code in institutional_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 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 package institutional_ocelot_0xrequest is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to malicious activities aimed at inflating developer reputation scores through the automatic generation of derivative packages. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in institutional_ocelot_0xrequest stems from its association with a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This activity not only pollutes the npm registry but also modifies the package.json file to remove private flags and alter version numbers. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may inadvertently expose their applications to further vulnerabilities.

How To Fix

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

npm uninstall institutional_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 avoid using the institutional_ocelot_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The institutional_ocelot_0xrequest package poses a significant security risk due to its association with malicious activities aimed at manipulating the npm registry. It is essential for developers to take proactive measures by removing the affected package and utilizing tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for institutional_ocelot_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can identify if your application is impacted. You can also use the Vulert playground at Vulert Scanner without signing up.

Using compromised packages can expose your application to security vulnerabilities, data breaches, and unauthorized access, potentially leading to significant damage.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

Immediately uninstall the institutional_ocelot_0xrequest package and review your project's dependencies for any other potentially compromised packages.

How To Fix

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

npm uninstall institutional_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