Malicious Code Injection in blpnhs-devapptea: A Threat to npm Ecosystem
Summary
MAL-2025-100026: Malicious code in blpnhs-devapptea (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
Background
The package blpnhs-devapptea is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in blpnhs-devapptea stems from its inclusion in a campaign that deploys autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall blpnhs-devappteaIf 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 workaround, consider using a package-lock.json file to monitor your dependencies. This file can help you track the versions of packages in your project and identify any potentially malicious packages. Additionally, you can use Vulert to monitor and alert for open-source vulnerabilities in real-time without requiring access to the code or installation.
Conclusion
The blpnhs-devapptea package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security. Utilizing tools like Vulert can aid in monitoring for vulnerabilities effectively.
See every vulnerability recorded for blpnhs-devapptea →
FAQ
blpnhs-devapptea is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and functionality.
You should uninstall the blpnhs-devapptea package immediately and check for any dependencies that may rely on it.
Yes, you can use tools like Vulert to monitor your package dependencies for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
