Malicious Code Injection in namadata-naururl-nagama: A Threat to npm Ecosystem

namadata-naururl-nagama Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161783: Malicious code in namadata-naururl-nagama (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 package 'namadata-naururl-nagama' 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 npm with malicious packages. These packages often include scripts designed to manipulate the npm registry and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in 'namadata-naururl-nagama' stems from its inclusion in a campaign that utilizes malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the pollution of the npm registry. This can result in unauthorized access to sensitive data and compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall namadata-naururl-nagama

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 use the following command to prevent the installation of this malicious package: 'npm install --no-optional'. This command will skip the installation of optional dependencies, which may include the vulnerable package.

Conclusion

The 'namadata-naururl-nagama' package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for namadata-naururl-nagama →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repackages them, leading to potential security risks.

You can check your application for vulnerabilities using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

The risks include unauthorized access to sensitive data, pollution of the npm registry, and potential exploitation of your application.

There is no specific patch for this package; the recommended action is to uninstall it and ensure your dependencies are up to date.

If you have installed the package, you should uninstall it immediately using 'npm uninstall namadata-naururl-nagama' and review your project for any other potentially vulnerable packages.

How To Fix

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

npm uninstall namadata-naururl-nagama

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