Malicious Code Injection in flaviosantos Package: A Threat to npm Users

flaviosantos Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171229: Malicious code in flaviosantos (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 flaviosantos package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to provide specific functionalities to developers. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security concerns for users who may unknowingly install it.

Vulnerability Detail

The vulnerability in the flaviosantos package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that automatically modify the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes variants to clutter the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access, and the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall flaviosantos

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 measure, you can avoid using the flaviosantos package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The flaviosantos package poses a significant security risk due to its malicious code designed to manipulate the npm registry. Users are advised to uninstall this package immediately and monitor their applications for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for flaviosantos →

Share this vulnerability

FAQ

The flaviosantos package is a JavaScript package available on npm, intended for use in various applications. However, it has been compromised and is now associated with malicious activities.

You can use Vulert, which monitors open-source vulnerabilities in your software using just the package-lock.json file. Visit the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed the flaviosantos package, you should uninstall it immediately using the command 'npm uninstall flaviosantos' and check for any other dependencies that may have been affected.

Yes, using compromised packages can lead to data breaches, unauthorized access to your application, and can compromise the integrity of your entire project.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall flaviosantos

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