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

syahmuda-poke47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166646: Malicious code in syahmuda-poke47 (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-poke47 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 numerous malicious activities. The primary function of such packages is to facilitate the automatic generation and publication of derivative packages, often with the intent of inflating developer reputation scores for token rewards. The presence of malicious code within this package poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in syahmuda-poke47 originates from its association with a malicious campaign that employs autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential data breaches, and a degraded developer reputation system within the npm ecosystem.

How To Fix

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

npm uninstall syahmuda-poke47

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 avoid using syahmuda-poke47 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The syahmuda-poke47 package poses a significant security risk due to its malicious code designed to manipulate npm package integrity. It is crucial for developers to remove this package, monitor their dependencies for vulnerabilities, and utilize tools like Vulert for real-time alerts on open-source vulnerabilities.

See every vulnerability recorded for syahmuda-poke47 →

Share this vulnerability

FAQ

syahmuda-poke47 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to compromised package integrity, potential data breaches, and pollution of the npm registry, which may affect the reliability of your project's dependencies.

You should remove the syahmuda-poke47 package from your project and monitor for any updates or patches that may address the vulnerability.

You can use tools like npm audit to check for vulnerabilities in your project's dependencies. Additionally, consider using Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

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-poke47

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