Malicious Code Injection in frightened_cardinal_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102939: Malicious code in frightened_cardinal_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 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 'frightened_cardinal_0xrequest' 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. These packages often contain scripts that automatically generate and publish derivative packages, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the 'frightened_cardinal_0xrequest' package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload can inflate developer reputation scores fraudulently, posing risks such as the introduction of untrusted code into applications that rely on this package.

How To Fix

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

npm uninstall frightened_cardinal_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 remove the 'frightened_cardinal_0xrequest' package from your project by executing: 'npm uninstall frightened_cardinal_0xrequest'. This will prevent any malicious code from executing while you assess alternative packages or wait for a fixed version.

Conclusion

The 'frightened_cardinal_0xrequest' package poses a significant security risk due to its malicious code that alters package configurations and inflates developer reputation scores. It is crucial to take immediate action by updating or removing the package to safeguard your application.

See every vulnerability recorded for frightened_cardinal_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.

The vulnerability can lead to the introduction of untrusted code, potentially compromising your application's security.

You can use Vulert's playground at Vulert Scanner to monitor and alert for vulnerabilities in your application without needing to sign up.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

Detailed information can be found in the vulnerability report and through the package's repository on npm.

How To Fix

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

npm uninstall frightened_cardinal_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