Malicious Code Injection in modirai-igo-jaii: A Threat to npm Users

modirai-igo-jaii Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160703: Malicious code in modirai-igo-jaii (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

modirai-igo-jaii is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The malicious behavior of this package includes the automatic generation and publication of variants with altered metadata, which can lead to significant pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file. These modifications remove private flags, change version numbers, and generate random package names, which can lead to the proliferation of malicious packages in the npm registry. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall modirai-igo-jaii

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 modirai-igo-jaii package from your project by executing: npm uninstall modirai-igo-jaii. This will prevent any potential malicious behavior associated with the package until a fix is applied.

Conclusion

The modirai-igo-jaii package poses a significant security risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for modirai-igo-jaii →

Share this vulnerability

FAQ

modirai-igo-jaii is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

If you have installed modirai-igo-jaii, it is recommended to uninstall it immediately and update your dependencies to ensure your project is secure.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly updating your dependencies, using tools to monitor for vulnerabilities, and reviewing package sources can help prevent similar issues in the future.

How To Fix

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

npm uninstall modirai-igo-jaii

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