Malicious Code Injection in historic_kite_0xrequest Package - npm Vulnerability

historic_kite_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103730: Malicious code in historic_kite_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 historic_kite_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions within the npm registry but has been compromised to include malicious scripts that manipulate package metadata. Its primary function is to support developers in managing their packages, but its vulnerability has led to significant security concerns.

Vulnerability Detail

The vulnerability in the historic_kite_0xrequest package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. This behavior is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry and potential exploitation of unsuspecting developers. The origin of this vulnerability is linked to a broader campaign that floods npm with compromised packages.

How To Fix

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

npm uninstall historic_kite_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 prevent the installation of the compromised package by using the following command to uninstall it: npm uninstall historic_kite_0xrequest. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The historic_kite_0xrequest package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for historic_kite_0xrequest →

Share this vulnerability

FAQ

The historic_kite_0xrequest package is an npm package associated with the tea.xyz token reward campaign, designed to assist developers in managing their packages.

The vulnerability allows malicious code to alter your package metadata, potentially leading to security risks and pollution of the npm registry.

If you have installed the historic_kite_0xrequest package, it is recommended to uninstall it immediately and monitor your project for any unusual behavior.

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

To prevent similar vulnerabilities, regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions.

How To Fix

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

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