Malicious Code Injection in namae-naua-maiso Package: A Threat to npm Users

namae-naua-maiso Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161814: Malicious code in namae-naua-maiso (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 namae-naua-maiso package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that targets developers by flooding the npm registry with harmful packages designed to manipulate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the namae-naua-maiso package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This behavior can lead to developers unknowingly using compromised packages, which can compromise their applications and lead to security breaches.

How To Fix

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

npm uninstall namae-naua-maiso

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 namae-naua-maiso package and any other packages that are part of the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to help identify vulnerabilities in your dependencies.

Conclusion

The namae-naua-maiso package poses a significant threat to developers using npm due to its malicious behavior. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.

See every vulnerability recorded for namae-naua-maiso →

Share this vulnerability

FAQ

The namae-naua-maiso package is an npm package that has been identified as part of a malicious campaign targeting developers by flooding the npm registry with harmful packages.

If your application uses the namae-naua-maiso package, it may be at risk of security breaches due to the malicious modifications made to the package.json file and the potential for using compromised code.

You should uninstall the namae-naua-maiso package immediately using 'npm uninstall namae-naua-maiso' and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, helping you stay informed about potential threats.

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

How To Fix

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

npm uninstall namae-naua-maiso

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