Malicious Code Injection in syahlan-poke17: A Threat to npm Users
Summary
MAL-2025-166514: Malicious code in syahlan-poke17 (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-poke17' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious code that modifies package metadata.
Vulnerability Detail
The vulnerability in 'syahlan-poke17' originates from its malicious payload, which alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code is part of a broader scheme to exploit the npm ecosystem for fraudulent purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke17
If 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 remove the 'syahlan-poke17' package from your project by executing the command: 'npm uninstall syahlan-poke17'. This will prevent any malicious code from executing in your environment.
Conclusion
The 'syahlan-poke17' package poses a significant risk due to its malicious code that alters package metadata and republish variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential exploitation.
See every vulnerability recorded for syahlan-poke17 →
FAQ
The main issue is the presence of malicious code that modifies package metadata and republish variants to the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you cannot update the package, it is recommended to uninstall it from your project to mitigate the risk.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.
Failing to address this vulnerability may lead to the compromise of your project's integrity, as malicious code can affect other packages and overall application security.