Malicious Code Injection in syahlan-poke32: A Threat to npm Packages
Summary
MAL-2025-166531: Malicious code in syahlan-poke32 (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 'syahlan-poke32' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in this campaign, is engineered to automatically generate and publish derivative packages, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'syahlan-poke32' stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke32If 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 a package-lock.json file to lock your dependencies to known safe versions. This can prevent the installation of the malicious package until a fix is implemented. You can also monitor your project for vulnerabilities using tools like Vulert, which checks your package-lock.json for known issues.
Conclusion
The 'syahlan-poke32' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for syahlan-poke32 →
FAQ
The impact includes potential exposure to malicious code, which can compromise application security and inflate developer reputation scores fraudulently.
You can use tools like Vulert to analyze your package-lock.json file for vulnerabilities related to syahlan-poke32.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
Immediately uninstall the package using 'npm uninstall syahlan-poke32' and check for any other affected packages.
Yes, but it is crucial to stay vigilant by regularly updating your packages and using security tools to monitor for vulnerabilities.
