Malicious Code Injection in manuk-nai-ignunaa Package: A Threat to npm Users

manuk-nai-ignunaa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160011: Malicious code in manuk-nai-ignunaa (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 manuk-nai-ignunaa package 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 the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish derivative packages with the intent to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the manuk-nai-ignunaa package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem and potentially affect developers who unknowingly use these packages.

How To Fix

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

npm uninstall manuk-nai-ignunaa

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 manuk-nai-ignunaa package from your project by executing the command: 'npm uninstall manuk-nai-ignunaa'. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The manuk-nai-ignunaa package poses a significant risk to npm users due to its malicious code designed to manipulate package metadata. It is essential to stay vigilant, regularly update dependencies, and utilize tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for manuk-nai-ignunaa →

Share this vulnerability

FAQ

The manuk-nai-ignunaa package is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for fraudulent purposes.

You can check if your project is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json without needing to sign up.

Using the manuk-nai-ignunaa package can lead to the pollution of the npm registry, compromise the integrity of your project, and potentially expose your application to further vulnerabilities.

Regularly updating your dependencies, using tools like Vulert for monitoring vulnerabilities, and auditing your packages can help prevent such issues.

If you have used the manuk-nai-ignunaa package, it is crucial to uninstall it immediately and check your project for any potential impacts. Consider using alternative packages that are well-reviewed and maintained.

How To Fix

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

npm uninstall manuk-nai-ignunaa

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