Malicious Code Injection in syahlan-poke3: A Threat to npm Ecosystem
Summary
MAL-2025-166528: Malicious code in syahlan-poke3 (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-poke3' 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, thereby posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'syahlan-poke3' stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants of the package to pollute the npm registry, making it difficult for developers to identify legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke3If 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-poke3' package from your project by executing the command: 'npm uninstall syahlan-poke3'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'syahlan-poke3' package presents a significant vulnerability due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for syahlan-poke3 →
FAQ
The vulnerability can lead to unauthorized modifications of your project's package.json file, potentially compromising your application's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks associated with the vulnerability.
While specific exploits may not be publicly documented, the nature of the vulnerability allows for potential abuse in manipulating package metadata and flooding the npm registry.
Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
