Malicious Code Injection in franciscojunior Package - npm Vulnerability
Summary
MAL-2025-171231: Malicious code in franciscojunior (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The franciscojunior package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the franciscojunior package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputation inflation for malicious actors and compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall franciscojuniorIf 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 prevent the installation of the franciscojunior package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time without requiring installation.
Conclusion
The franciscojunior package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to take immediate action to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for franciscojunior →
FAQ
franciscojunior is an npm package that is part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the franciscojunior package from your project and check for any potential impacts on your application.
You can use Vulert to monitor your application for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
