Malicious Code Injection in modirai-igno-jaimmagi: A Threat to npm Ecosystem

modirai-igno-jaimmagi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160663: Malicious code in modirai-igno-jaimmagi (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

modirai-igno-jaimmagi 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 nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the registry.

Vulnerability Detail

The vulnerability in modirai-igno-jaimmagi originates from its design to execute autopublish scripts that manipulate the package.json file. This manipulation includes removing private flags, altering version numbers, and generating random package names, which can lead to a significant increase in the number of malicious packages in the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly integrate these packages into their projects, as well as a degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall modirai-igno-jaimmagi

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, consider using a package auditing tool to scan your project for vulnerabilities. You can use npm audit to identify and address any security issues in your dependencies. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The modirai-igno-jaimmagi package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and repopulates the registry with harmful variants. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for modirai-igno-jaimmagi →

Share this vulnerability

FAQ

modirai-igno-jaimmagi is an npm package involved in a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately and check your project for any unauthorized changes made by the malicious scripts.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall modirai-igno-jaimmagi

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