Malicious Code Injection in syahlan-poke60: A Threat to npm Ecosystem
Summary
MAL-2025-166562: Malicious code in syahlan-poke60 (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-poke60' 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 linked to malicious activities aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The presence of such malicious code poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'syahlan-poke60' originates from its association with a malicious campaign that employs scripts to modify the package.json file. These modifications include removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants that pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes users to potential security risks and untrusted code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke60If 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-poke60' package from your project by executing the command: 'npm uninstall syahlan-poke60'. This will help prevent any potential exploitation of the vulnerability until a patch is available.
Conclusion
The 'syahlan-poke60' package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry with untrusted packages. It is crucial for developers to stay vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for syahlan-poke60 →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages it under random names, compromising the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using syahlan-poke60 can expose your application to untrusted code, leading to potential security breaches and data integrity issues.
Regularly update your packages, utilize tools like Vulert for monitoring vulnerabilities, and review package dependencies for any known issues.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
