Malicious Code Injection in syahmuda-poke38 Package - npm Vulnerability

syahmuda-poke38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166636: Malicious code in syahmuda-poke38 (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 syahmuda-poke38 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities to inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the syahmuda-poke38 package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is executed through autopublish scripts that continuously republish variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes developers to publish numerous packages, often at the expense of security and integrity.

How To Fix

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

npm uninstall syahmuda-poke38

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 avoid using the syahmuda-poke38 package until a patched version is released. Additionally, consider using npm audit to check for vulnerabilities in your project and remove any affected packages.

Conclusion

The syahmuda-poke38 package has been identified as a vector for malicious code injection, posing significant risks to developers and applications. It is essential to stay informed about such vulnerabilities and take proactive measures to secure your projects.

See every vulnerability recorded for syahmuda-poke38 →

Share this vulnerability

FAQ

syahmuda-poke38 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the pollution of the npm registry, potentially causing conflicts and security issues in your application.

You should update the package to the latest version or remove it from your project until a secure version is available.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

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