Malicious Code Injection in syahlan-poke71: A Threat to npm Ecosystem
Summary
MAL-2025-166574: Malicious code in syahlan-poke71 (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-poke71' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'syahlan-poke71' originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate 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 ramifications include a loss of trust in the npm ecosystem and the risk of developers inadvertently using compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke71If 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, avoid using the 'syahlan-poke71' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The 'syahlan-poke71' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to maintain the security of their applications. By following the recommended steps, developers can protect their projects from potential risks.
See every vulnerability recorded for syahlan-poke71 →
FAQ
The main risk is that it contains malicious code that can modify your project's package.json file, potentially leading to the use of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.
You should uninstall the package immediately using 'npm uninstall syahlan-poke71' and audit your project for any other potentially compromised packages.
Yes, consider using other reputable packages that provide similar functionality without the associated risks. Always verify the package's integrity before use.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
