Malicious Code Injection in oejlbn-devapptea Package: A Threat to npm Users
Summary
MAL-2025-106553: Malicious code in oejlbn-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 oejlbn-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to its malicious intent, posing significant risks to users who may unknowingly integrate it into their projects.
Vulnerability Detail
The vulnerability in the oejlbn-devapptea package stems from its inclusion in a campaign that utilizes autopublish scripts to modify package.json files. This malicious code removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security breaches, loss of control over package versions, and an inflated reputation score for malicious actors. This vulnerability is particularly concerning as it can affect the integrity of the npm ecosystem and the trustworthiness of packages within it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall oejlbn-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 prevent the installation of the oejlbn-devapptea package by using npm's package-lock.json file to lock dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which allows you to check for open-source vulnerabilities without requiring code access. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.
Conclusion
The oejlbn-devapptea package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and inflate reputation scores. Users are advised to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying vigilant and informed is crucial to maintaining the security of your software projects.
See every vulnerability recorded for oejlbn-devapptea →
FAQ
oejlbn-devapptea is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
This vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing security risks.
You should immediately remove the oejlbn-devapptea package from your project and check for any other affected packages in your dependency tree.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities. Visit https://vulert.com for more information.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
