Malicious Code Vulnerability in seblakkuah29: Exploiting npm Packages for Reputation Inflation
Summary
MAL-2025-108466: Malicious code in seblakkuah29 (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 'seblakkuah29' is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The malicious behavior of this package poses a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'seblakkuah29' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as a degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall seblakkuah29If 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 workaround, you can avoid using the 'seblakkuah29' package altogether. If you have already installed it, you can uninstall it using the command: npm uninstall seblakkuah29.
Conclusion
The 'seblakkuah29' package presents a significant security risk due to its malicious code designed to manipulate npm package reputation. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software projects.
See every vulnerability recorded for seblakkuah29 →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.
You should uninstall the package immediately using the command: npm uninstall seblakkuah29.
Yes, using this package can lead to security risks and contribute to the degradation of the npm ecosystem due to the proliferation of malicious packages.
Regularly monitor your dependencies using tools like Vulert and ensure to review package sources before installation to avoid malicious packages.
