Malicious Code Injection in mahesa-kupang11-riris Package

mahesa-kupang11-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88143: Malicious code in mahesa-kupang11-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 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 mahesa-kupang11-riris package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability in the mahesa-kupang11-riris package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages in their projects.

How To Fix

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

npm uninstall mahesa-kupang11-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 workaround, you can monitor your project for any unintended changes by using tools like Vulert. Vulert allows you to check your package-lock.json file for vulnerabilities without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The mahesa-kupang11-riris package contains malicious code that compromises the integrity of the npm registry. It is crucial for developers to be aware of such vulnerabilities and take immediate action to remove affected packages from their projects. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for mahesa-kupang11-riris →

Share this vulnerability

FAQ

The mahesa-kupang11-riris package is an npm package associated with the tea.xyz token reward campaign, which is known for flooding the npm registry with malicious packages.

This vulnerability can lead to the proliferation of unwanted packages in your application, potentially compromising its security and integrity.

You should uninstall the mahesa-kupang11-riris package immediately using 'npm uninstall mahesa-kupang11-riris' and monitor your project for any other vulnerabilities.

Yes, you can use tools like Vulert to monitor your dependencies for vulnerabilities in real-time, helping you to catch issues before they affect your application.

Due to the malicious nature of the mahesa-kupang11-riris package, it is recommended to avoid using it altogether rather than looking for a patched version.

How To Fix

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

npm uninstall mahesa-kupang11-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