Malicious Code Injection in modirai-igo-jaimgi Package

modirai-igo-jaimgi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160704: Malicious code in modirai-igo-jaimgi (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

The modirai-igo-jaimgi package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the modirai-igo-jaimgi package stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior can inflate developer reputation scores fraudulently and may expose users to further security risks, including the installation of compromised packages.

How To Fix

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

npm uninstall modirai-igo-jaimgi

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 workaround, you can temporarily avoid using the modirai-igo-jaimgi package by removing it from your dependencies. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The modirai-igo-jaimgi package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for modirai-igo-jaimgi →

Share this vulnerability

FAQ

The modirai-igo-jaimgi package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

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

If you have installed the modirai-igo-jaimgi package, it is crucial to remove it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

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 modirai-igo-jaimgi

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