Malicious Code Injection in wee_krill_0xrequest Package

wee_krill_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110787: Malicious code in wee_krill_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 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 wee_krill_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is often included in projects to facilitate specific functionalities or integrations. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the wee_krill_0xrequest package stems from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The malicious payload not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall wee_krill_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, avoid using the wee_krill_0xrequest package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The wee_krill_0xrequest package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for wee_krill_0xrequest →

Share this vulnerability

FAQ

The wee_krill_0xrequest package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

You should uninstall the wee_krill_0xrequest package immediately and monitor your application for any unusual behavior.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign 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 wee_krill_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