Malicious Code Injection in bjlnfu-devapptea Package: A Threat to npm Users
Summary
MAL-2025-99997: Malicious code in bjlnfu-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 bjlnfu-devapptea package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to facilitate token rewards through automatic publishing scripts, which can lead to the proliferation of malicious variants. Its primary functionality revolves around generating and publishing derivative packages, but its vulnerability exposes users to potential security risks.
Vulnerability Detail
The bjlnfu-devapptea package contains malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm ecosystem, making it difficult for developers to trust legitimate packages. The origin of this vulnerability is traced back to the package's design, which was intended to exploit the npm registry for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bjlnfu-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 temporary workaround, you can avoid using the bjlnfu-devapptea package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The bjlnfu-devapptea package poses a significant threat to npm users due to its malicious code that modifies package metadata and floods the registry with harmful variants. It is essential to remove this package and adopt best practices for dependency management to safeguard your projects.
See every vulnerability recorded for bjlnfu-devapptea →
FAQ
The bjlnfu-devapptea package is part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages for token rewards.
The vulnerability can lead to the pollution of your project's dependencies, making it difficult to manage and trust the packages you are using.
You should uninstall the bjlnfu-devapptea package immediately using the command 'npm uninstall bjlnfu-devapptea' and review your project's dependencies for any other malicious packages.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and only install packages from trusted sources.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
