Malicious Code Injection in namadata-munaroha-manukangifad Package

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161771: Malicious code in namadata-munaroha-manukangifad (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 namadata-munaroha-manukangifad package 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 known to flood the npm registry with numerous derivative packages. Its primary functionality is to facilitate the generation and publication of packages, but it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the namadata-munaroha-manukangifad package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names that are Indonesian-themed or in English. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potentially damaging the reputation of legitimate developers. This issue originates from the package being part of a broader campaign aimed at exploiting npm for token rewards.

How To Fix

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

npm uninstall namadata-munaroha-manukangifad

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 namadata-munaroha-manukangifad package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The namadata-munaroha-manukangifad package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for namadata-munaroha-manukangifad →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may damage your project's reputation if malicious packages are published under your name.

You should uninstall the package immediately using npm uninstall namadata-munaroha-manukangifad and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall namadata-munaroha-manukangifad

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