Malicious Code Injection in syahlan-poke100: A Threat to npm Ecosystem
Summary
MAL-2025-166497: Malicious code in syahlan-poke100 (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-poke100' is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include 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-poke100' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages within the ecosystem, potentially affecting any application that relies on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke100If 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-poke100' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any changes in the package-lock.json file to ensure no malicious packages are introduced.
Conclusion
The 'syahlan-poke100' package poses a significant threat due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and informed is key to maintaining the integrity of the npm ecosystem.
See every vulnerability recorded for syahlan-poke100 →
FAQ
The primary risk is the injection of malicious code that modifies package metadata, leading to potential security vulnerabilities and pollution of the npm registry.
You can check your project's package-lock.json file for the presence of 'syahlan-poke100'. Additionally, you can use Vulert to monitor and alert for vulnerabilities in real-time.
You should uninstall the package immediately using 'npm uninstall syahlan-poke100' and check for any dependencies that may rely on it.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
