Malicious Code Vulnerability in franciscosouza Package

franciscosouza Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171232: Malicious code in franciscosouza (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The franciscosouza package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of derivative packages. The malicious behavior includes modifying package metadata and continuously republishing variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of the tea.xyz token reward campaign, which floods npm with malicious packages. It includes scripts that automatically generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names, which can lead to reputation damage for developers and potential security risks for users of these packages.

How To Fix

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

npm uninstall franciscosouza

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 franciscosouza package from your project by executing: npm uninstall franciscosouza. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The franciscosouza package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package to protect your projects from potential threats.

See every vulnerability recorded for franciscosouza →

Share this vulnerability

FAQ

The franciscosouza package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should immediately update or uninstall the package to mitigate the risks associated with this vulnerability.

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 franciscosouza

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