Malicious Code Injection in syahmuda-poke32: A Threat to npm Ecosystem
Summary
MAL-2025-166630: Malicious code in syahmuda-poke32 (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 'syahmuda-poke32' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with a token reward campaign that has been linked to the proliferation of malicious packages. Its functionality is compromised by the presence of scripts that manipulate package metadata and republish variants, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'syahmuda-poke32' stems from malicious code embedded within the package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names to inflate reputation scores for token rewards. The origin of this vulnerability is traced back to a campaign that floods the npm registry with derivative packages, leading to pollution of the registry and potential exploitation by malicious actors. The ramifications include compromised developer reputations, potential data breaches, and a general degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall syahmuda-poke32If 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 an immediate workaround, you can avoid using 'syahmuda-poke32' and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'syahmuda-poke32' package poses a significant risk due to its embedded malicious code, which can compromise the integrity of your project and the npm ecosystem. It is essential to take immediate action by uninstalling the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for syahmuda-poke32 →
FAQ
'syahmuda-poke32' is an npm package that has been identified as containing malicious code aimed at manipulating package metadata.
The malicious code can alter your package.json file, leading to potential security risks and pollution of the npm registry.
You should uninstall 'syahmuda-poke32' immediately and monitor your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
