Malicious Code Injection in syahmuda-poke41: npm Package Vulnerability
Summary
MAL-2025-166640: Malicious code in syahmuda-poke41 (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 syahmuda-poke41 package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in syahmuda-poke41 stems from its 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 behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahmuda-poke41If 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 avoid using the syahmuda-poke41 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of malicious packages.
Conclusion
The syahmuda-poke41 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to be vigilant and remove such packages from their projects to maintain the security of their applications. Utilizing tools like Vulert can aid in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for syahmuda-poke41 →
FAQ
syahmuda-poke41 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
If you have already used the syahmuda-poke41 package, it is crucial to remove it from your project and check for any other potentially malicious packages.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities by analyzing your package-lock.json file.
