Malicious Code Injection in syahmuda-poke31: A Threat to npm Ecosystem

syahmuda-poke31 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166629: Malicious code in syahmuda-poke31 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'syahmuda-poke31' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'syahmuda-poke31' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the broader malicious activity targeting npm packages, where scripts are employed to automate the creation of harmful derivatives, compromising the security and reliability of the npm ecosystem.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall syahmuda-poke31

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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'syahmuda-poke31' or any of its derivatives. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'syahmuda-poke31' package represents a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance your ability to detect and respond to such threats effectively.

See every vulnerability recorded for syahmuda-poke31 →

Share this vulnerability

FAQ

'syahmuda-poke31' is a malicious npm package that is part of a campaign to manipulate the npm registry and inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry with malicious packages, potentially compromising the security and integrity of your project.

You should uninstall 'syahmuda-poke31' immediately and ensure your project does not reference it in package.json.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without requiring access to the code or installation.

Regularly audit your dependencies, use tools like Vulert, and stay informed about known vulnerabilities in the npm ecosystem.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall syahmuda-poke31

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback