Malicious Code Injection in seblakkuah4: A Threat to npm Users
Summary
MAL-2025-108477: Malicious code in seblakkuah4 (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
seblakkuah4 is an npm package that appears to be part of a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata and republish variants, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in seblakkuah4 originates from its inclusion in a campaign that floods the npm ecosystem with malicious packages. These packages contain scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the security of applications relying on these packages, potentially leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah4If 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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The seblakkuah4 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for seblakkuah4 →
FAQ
seblakkuah4 is an npm package involved in a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.
You should remove the seblakkuah4 package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
