Malicious Code Injection in namae-nadugsua-mitos: A Threat to npm Ecosystem

namae-nadugsua-mitos Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161799: Malicious code in namae-nadugsua-mitos (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'namae-nadugsua-mitos' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers by inflating reputation scores through deceptive practices.

How To Fix

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

npm uninstall namae-nadugsua-mitos

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 prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. Ensure that your package-lock.json does not include 'namae-nadugsua-mitos'. You can also use the following command to audit your packages for vulnerabilities: 'npm audit'.

Conclusion

The 'namae-nadugsua-mitos' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for namae-nadugsua-mitos →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and repackages itself under random names, which can lead to npm registry pollution.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall namae-nadugsua-mitos' and audit your other dependencies for similar vulnerabilities.

There are no patches available for this specific package as it is malicious. The best course of action is to remove it from your project.

Regularly audit your dependencies using 'npm audit', keep your packages updated, and monitor your project with tools like Vulert to catch vulnerabilities early.

How To Fix

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

npm uninstall namae-nadugsua-mitos

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