Malicious Code Injection in spicy_unicorn_0xrequest Package

spicy_unicorn_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109013: Malicious code in spicy_unicorn_0xrequest (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spicy_unicorn_0xrequest package is part of the npm ecosystem, primarily used for various web development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the spicy_unicorn_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include potential exposure to further malicious code and a compromised development environment.

How To Fix

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

npm uninstall spicy_unicorn_0xrequest

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 spicy_unicorn_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The spicy_unicorn_0xrequest package poses a significant security risk due to its malicious code that alters project files and repopulates the npm registry with potentially harmful variants. It is crucial to remove this package and monitor your projects for vulnerabilities.

See every vulnerability recorded for spicy_unicorn_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The malicious code can modify your package.json, remove private flags, and continuously republish variants, potentially exposing your project to further vulnerabilities.

You should uninstall the spicy_unicorn_0xrequest package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and stay informed about the packages you include in your projects.

How To Fix

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

npm uninstall spicy_unicorn_0xrequest

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