Malicious Code Injection in modira-fuoa-janur Package

modira-fuoa-janur Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160588: Malicious code in modira-fuoa-janur (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 modira-fuoa-janur package is part of the npm ecosystem, often utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the modira-fuoa-janur package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall modira-fuoa-janur

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 remove the modira-fuoa-janur package from your project by executing: 'npm uninstall modira-fuoa-janur'. This will prevent any malicious code from executing in your application until a secure version is available.

Conclusion

The modira-fuoa-janur package contains a significant vulnerability due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by uninstalling the package and monitoring for updates to ensure the security of their applications.

See every vulnerability recorded for modira-fuoa-janur →

Share this vulnerability

FAQ

The modira-fuoa-janur package is an npm package that is part of a campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the modification of your package.json file, potentially exposing your application to security risks and polluting the npm registry.

If you have installed the modira-fuoa-janur package, it is crucial to uninstall it immediately and monitor for any updates or patches.

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

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 modira-fuoa-janur

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