Malicious Code Injection in modirai-igimamafo-jagaigg Package

modirai-igimamafo-jagaigg Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160648: Malicious code in modirai-igimamafo-jagaigg (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 modirai-igimamafo-jagaigg package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the modirai-igimamafo-jagaigg package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The origin of this vulnerability is linked to the broader issue of automated scripts that flood the npm ecosystem with low-quality or harmful packages.

How To Fix

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

npm uninstall modirai-igimamafo-jagaigg

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-igimamafo-jagaigg package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The modirai-igimamafo-jagaigg package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to uninstall this package and monitor your projects for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your dependencies.

See every vulnerability recorded for modirai-igimamafo-jagaigg →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The malicious code can modify your package.json file, remove private flags, and publish harmful variants, potentially compromising your project's security.

You should uninstall the package immediately using 'npm uninstall modirai-igimamafo-jagaigg' and check for any other affected packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall modirai-igimamafo-jagaigg

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