Malicious Code Injection in iomodra-fuoa-ja Package: A Threat to npm Users

iomodra-fuoa-ja Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156802: Malicious code in iomodra-fuoa-ja (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 iomodra-fuoa-ja package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the iomodra-fuoa-ja package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically modify their own package.json files, removing private flags and changing version numbers. This results in the generation of numerous derivative packages with randomized names, ultimately polluting the npm registry and inflating developer reputation scores. The malicious payload can lead to unintended consequences for developers who may unknowingly use these compromised packages, exposing their applications to further risks.

How To Fix

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

npm uninstall iomodra-fuoa-ja

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 iomodra-fuoa-ja package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The iomodra-fuoa-ja package poses a significant security risk due to its malicious code injection. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for iomodra-fuoa-ja →

Share this vulnerability

FAQ

The iomodra-fuoa-ja package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and functionality.

If you have installed the iomodra-fuoa-ja package, it is recommended to remove it immediately and update your dependencies to ensure your application is secure.

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

To prevent future vulnerabilities, regularly update your packages, use trusted sources, and consider implementing security tools that can scan for known vulnerabilities.

How To Fix

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

npm uninstall iomodra-fuoa-ja

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