Malicious Code Injection in namadata-munaroha-nagamfa Package

namadata-munaroha-nagamfa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161781: Malicious code in namadata-munaroha-nagamfa (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-nagamfa package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate certain functionalities within applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability stems from the package being associated with a malicious campaign that generates and publishes derivative packages with randomized names. This is done through scripts that modify the package.json file, removing private flags and changing version numbers. The malicious payload can lead to the pollution of the npm registry, affecting the integrity of the ecosystem and potentially compromising applications that depend on these packages.

How To Fix

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

npm uninstall namadata-munaroha-nagamfa

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-nagamfa package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.

Conclusion

The namadata-munaroha-nagamfa package poses a significant security risk due to its association with a malicious campaign. It is crucial for developers to be vigilant about the packages they use and to take immediate action to mitigate any risks associated with this vulnerability.

See every vulnerability recorded for namadata-munaroha-nagamfa →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing system.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to security risks.

You should uninstall the package immediately using 'npm uninstall namadata-munaroha-nagamfa' and look for secure alternatives.

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

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

How To Fix

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

npm uninstall namadata-munaroha-nagamfa

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