Malicious Code Injection in syahlan-poke31: A Threat to npm Ecosystem
Summary
MAL-2025-166530: Malicious code in syahlan-poke31 (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-poke31' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'syahlan-poke31' originates from its malicious code 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 derivative packages, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it crucial for developers to be aware of such threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke31If 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 'syahlan-poke31' package and monitor your project for any dependencies that may indirectly rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities.
Conclusion
The 'syahlan-poke31' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for syahlan-poke31 →
FAQ
'syahlan-poke31' is an npm package that has been identified as containing malicious code aimed at manipulating package metadata.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should remove the package immediately and check for any other dependencies that may be affected.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
