Malicious Code Injection in ocha-mangut20-riris: A Threat to npm Users

ocha-mangut20-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89005: Malicious code in ocha-mangut20-riris (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

ocha-mangut20-riris is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with spammy packages, potentially harming developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the ocha-mangut20-riris package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign that aims to inflate developer reputation scores for token rewards, posing risks of registry pollution and developer trust erosion.

How To Fix

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

npm uninstall ocha-mangut20-riris

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, avoid using the ocha-mangut20-riris package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The ocha-mangut20-riris package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for ocha-mangut20-riris →

Share this vulnerability

FAQ

ocha-mangut20-riris is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of packages.

The malicious code modifies your package.json file, potentially leading to the removal of private flags and the introduction of spammy package names, which can harm your project's integrity.

You should uninstall the package immediately using 'npm uninstall ocha-mangut20-riris' and monitor your project for any further vulnerabilities.

You can use Vulert, which allows you to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to access your code or install additional software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall ocha-mangut20-riris

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