Malicious Code Injection in modirai-ignono-jaimagi: A Threat to npm Packages

modirai-ignono-jaimagi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160699: Malicious code in modirai-ignono-jaimagi (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-ignono-jaimagi is an npm package that is part of a broader campaign targeting the npm registry. This package, like many others involved in the tea.xyz token reward scheme, is designed to manipulate the npm ecosystem by generating and publishing derivative packages. Its primary functionality is to serve as a token reward mechanism, but it has been compromised to include malicious code that affects its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in modirai-ignono-jaimagi stems from its association with a malicious campaign that uses autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to trust the packages they use.

How To Fix

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

npm uninstall modirai-ignono-jaimagi

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 modirai-ignono-jaimagi package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The modirai-ignono-jaimagi package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for modirai-ignono-jaimagi →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and publishes numerous derivative packages to inflate developer reputation scores.

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

You should uninstall the package immediately using 'npm uninstall modirai-ignono-jaimagi' and look for alternatives.

Yes, the impacts include the potential for package pollution in the npm registry and compromised integrity of your project's dependencies.

Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities, helping you maintain the security of your software.

How To Fix

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

npm uninstall modirai-ignono-jaimagi

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