Malicious Code Injection in seblakkuah14 Package - npm Vulnerability
Summary
MAL-2025-108451: Malicious code in seblakkuah14 (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 seblakkuah14 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality revolves around creating and managing these derivative packages, but it has been compromised to include malicious scripts.
Vulnerability Detail
The vulnerability in the seblakkuah14 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers by misrepresenting their contributions and reputation. The malicious payload is designed to execute autopublish scripts that automate these processes, making it difficult for developers to maintain control over their packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah14If 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 seblakkuah14 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The seblakkuah14 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unauthorized variants. It is essential for developers to take immediate action by removing the package and monitoring their projects for any signs of compromise. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for seblakkuah14 →
FAQ
The seblakkuah14 package is part of the npm ecosystem and is used for automatic generation and publication of derivative packages, often linked to token reward campaigns.
The vulnerability can lead to unauthorized changes in your package.json file, potentially harming your project's integrity and reputation in the npm registry.
You should uninstall the package immediately using 'npm uninstall seblakkuah14' and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities.
