Malicious Code Injection in syahlan-poke53: A Threat to npm Ecosystem
Summary
MAL-2025-166554: Malicious code in syahlan-poke53 (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-poke53' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'syahlan-poke53' originates from malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahlan-poke53
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-poke53' package from your project by executing: npm uninstall syahlan-poke53. This will prevent any malicious code from executing in your environment until a fix is available.
Conclusion
The 'syahlan-poke53' package poses a significant threat due to its malicious code that alters package metadata and repackages it under random names. It is crucial to take immediate action by updating or removing the package to safeguard your project and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for syahlan-poke53 →
FAQ
The vulnerability involves malicious code that alters package metadata 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.
If no patched version is available, it is advisable to remove the package from your project to mitigate risks.
The malicious code can lead to unauthorized changes in your project, potentially exposing sensitive information and affecting the stability of your application.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.