Malicious Code Vulnerability in munya-mipta-munaro Package

munya-mipta-munaro Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160983: Malicious code in munya-mipta-munaro (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 munya-mipta-munaro package is part of the npm ecosystem, often utilized in various JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers' reputations and polluting the registry.

Vulnerability Detail

The vulnerability in the munya-mipta-munaro package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. This behavior not only inflates developer reputation scores for token rewards but also compromises the integrity of the npm registry by introducing numerous unwanted packages. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall munya-mipta-munaro

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 munya-mipta-munaro package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package-lock.json file to ensure that no malicious packages are included.

Conclusion

The munya-mipta-munaro package contains a serious vulnerability that can lead to the modification of your project's package.json and the pollution of the npm registry. It is crucial to uninstall this package and monitor your dependencies for any malicious activity. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.

See every vulnerability recorded for munya-mipta-munaro →

Share this vulnerability

FAQ

The munya-mipta-munaro package is part of the npm ecosystem and is linked to a token reward campaign that floods the registry with malicious packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and floods the npm registry with unwanted packages.

You should uninstall the munya-mipta-munaro package immediately using the command npm uninstall munya-mipta-munaro.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

npm uninstall munya-mipta-munaro

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