Malicious Code Injection in dariobafirascroissantguette Package

dariobafirascroissantguette Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171087: Malicious code in dariobafirascroissantguette (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 'dariobafirascroissantguette' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. It is designed to inflate developer reputation scores by generating and publishing numerous derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the 'dariobafirascroissantguette' package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random names for packages, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data 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 dariobafirascroissantguette

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

Conclusion

The 'dariobafirascroissantguette' package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to take immediate action by updating or removing the package to protect your project from potential threats.

See every vulnerability recorded for dariobafirascroissantguette →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications of your package.json file and the potential for your project to be associated with malicious activities.

You should uninstall the package immediately and check your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall dariobafirascroissantguette

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