Malicious Code Injection in Roasted Vicuna Requirement Package

roasted_vicuna_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96388: Malicious code in roasted_vicuna_requirement (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'roasted_vicuna_requirement' package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that exploits npm's publishing system to inflate developer reputation scores through the automatic generation and publication of derivative packages. The vulnerability stems from the package's design, which allows for the manipulation of its contents and the npm registry.

Vulnerability Detail

The vulnerability in the 'roasted_vicuna_requirement' package involves the presence of malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, 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 dependency confusion, reputation damage for developers, and the proliferation of untrusted code in the ecosystem.

How To Fix

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

npm uninstall roasted_vicuna_requirement

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, consider removing the 'roasted_vicuna_requirement' package from your project until a secure version is released. You can uninstall it using the command: 'npm uninstall roasted_vicuna_requirement'. Additionally, monitor your package-lock.json file for any unexpected changes.

Conclusion

The 'roasted_vicuna_requirement' package poses a significant security risk due to its malicious code injection vulnerability. It is essential for developers to take immediate action by updating or removing the package and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for roasted_vicuna_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the introduction of malicious code, potentially compromising your application's 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 for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall roasted_vicuna_requirement

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