Malicious Code Injection in sparkling_kiwi_0xrequest Package

sparkling_kiwi_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108968: Malicious code in sparkling_kiwi_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 sparkling_kiwi_0xrequest package is part of the npm ecosystem, primarily used for handling HTTP requests in JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing system. This package is linked to the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages that aim to inflate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which 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 security risks, including the potential for developers to unknowingly use compromised packages, which may contain harmful code.

How To Fix

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

npm uninstall sparkling_kiwi_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 sparkling_kiwi_0xrequest package from your project by running: npm uninstall sparkling_kiwi_0xrequest. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The sparkling_kiwi_0xrequest package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package and monitoring for any future vulnerabilities.

See every vulnerability recorded for sparkling_kiwi_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for handling HTTP requests, but it has been compromised with malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, using a compromised package can introduce malicious code into your project, posing significant security risks.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

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