Malicious Code Injection in ocha-nasipecel35-ruro: A Threat to npm Ecosystem

ocha-nasipecel35-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106531: Malicious code in ocha-nasipecel35-ruro (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 Your last release was probably never penetration tested 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 'ocha-nasipecel35-ruro' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, but they pose significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

This vulnerability originates from malicious code embedded within the 'ocha-nasipecel35-ruro' package. The code modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications that depend on these packages. The ramifications include potential exposure to further malicious activities and a degradation of the npm ecosystem's trustworthiness.

How To Fix

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

npm uninstall ocha-nasipecel35-ruro

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 avoid using the 'ocha-nasipecel35-ruro' package and replace it with a trusted alternative. If you need to maintain functionality, consider using a local version of the package without the malicious code, but this should only be a short-term solution until the vulnerability is fully addressed.

Conclusion

The 'ocha-nasipecel35-ruro' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. Immediate action is required to remove this package and safeguard your applications. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for ocha-nasipecel35-ruro →

Share this vulnerability

FAQ

The main risk is the potential for malicious code to compromise your application and the integrity of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately and review your project's dependencies for any other potentially malicious packages.

Currently, there are no patches available for the 'ocha-nasipecel35-ruro' package, so the best course of action is to remove it.

Regularly audit your dependencies, use trusted sources for packages, and consider employing tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall ocha-nasipecel35-ruro

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