Malicious Code Injection in blankenship-tea-archive: npm Package Vulnerability
Summary
MAL-2025-100003: Malicious code in blankenship-tea-archive (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 blankenship-tea-archive package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the blankenship-tea-archive package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, leading to pollution of the npm registry. This can result in compromised package integrity, potential security risks for users, and a degradation of the overall quality of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall blankenship-tea-archiveIf 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 blankenship-tea-archive package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The blankenship-tea-archive package contains malicious code that poses significant risks to users and the npm ecosystem. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.
See every vulnerability recorded for blankenship-tea-archive →
FAQ
It is an npm package that is part of a token reward campaign and is known to contain malicious code.
The malicious code modifies your package.json file and can lead to the publication of compromised packages, affecting your project's integrity.
You should uninstall the blankenship-tea-archive package immediately and check your project for any other compromised dependencies.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
