Malicious Code Injection in seblakkuah27: A Threat to npm Ecosystem
Summary
MAL-2025-108464: Malicious code in seblakkuah27 (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 'seblakkuah27' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can lead to inflated developer reputation scores in exchange for token rewards. The malicious nature of this package poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'seblakkuah27' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. This behavior can result in developers unknowingly using compromised packages, which may lead to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah27If 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 'seblakkuah27' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify vulnerabilities.
Conclusion
The 'seblakkuah27' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json files and publishes harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for seblakkuah27 →
FAQ
The primary risk is that it modifies package.json files to remove private flags and publishes malicious variants, which can compromise the integrity of your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall seblakkuah27' and check for any dependencies that may be affected.
Yes, tools like npm audit and Vulert can help identify and manage vulnerabilities in your npm packages.
Using compromised packages can lead to data breaches, unauthorized access to systems, and damage to your project's reputation.
