Malicious Code Injection in namadata-munaroha-manu Package

namadata-munaroha-manu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161764: Malicious code in namadata-munaroha-manu (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-manu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to generate and publish derivative packages with randomized names, which can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the namadata-munaroha-manu 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. This behavior can pollute the npm registry and compromise the integrity of the ecosystem, potentially affecting developers who rely on these packages for their projects.

How To Fix

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

npm uninstall namadata-munaroha-manu

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 remove the namadata-munaroha-manu package from your project if it is not essential. You can do this by executing the command: 'npm uninstall namadata-munaroha-manu'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The namadata-munaroha-munaroha package contains malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for namadata-munaroha-manu →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should uninstall the package immediately and check for any other affected packages in your project.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

npm uninstall namadata-munaroha-manu

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