Malicious Code Injection in anouarfrenchie Package: npm Vulnerability Overview

anouarfrenchie Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170895: Malicious code in anouarfrenchie (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 anouarfrenchie 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 JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability in the anouarfrenchie package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The ramifications include the risk of executing malicious code and the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall anouarfrenchie

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 anouarfrenchie package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert to monitor for vulnerabilities.

Conclusion

The anouarfrenchie package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can enhance your ability to monitor for vulnerabilities and maintain the integrity of your applications.

See every vulnerability recorded for anouarfrenchie →

Share this vulnerability

FAQ

The anouarfrenchie package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

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

You should uninstall the anouarfrenchie package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Regularly auditing your dependencies and using tools like Vulert can help you monitor and alert for open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall anouarfrenchie

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