Malicious Code Vulnerability in tricky_hornet_0xrequest Package
Summary
MAL-2025-109832: Malicious code in tricky_hornet_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The tricky_hornet_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages. Its primary function is to facilitate the development and distribution of JavaScript applications, but it has been compromised to execute harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It includes scripts designed to automatically publish variants with randomized names, effectively removing private flags from package.json files and altering version numbers. This behavior can lead to the pollution of the npm registry and potentially compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tricky_hornet_0xrequestIf 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 tricky_hornet_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to detect any vulnerabilities in real-time.
Conclusion
The tricky_hornet_0xrequest package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. It is crucial to remove this package and monitor for vulnerabilities to maintain the integrity and security of your software.
See every vulnerability recorded for tricky_hornet_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to further security risks.
You should remove the tricky_hornet_0xrequest package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
