Malicious Code Injection in syahlan-poke78: A Threat to npm Ecosystem

syahlan-poke78 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166581: Malicious code in syahlan-poke78 (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'syahlan-poke78' 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 a series of malicious activities aimed at inflating developer reputation scores. The package is designed to generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in 'syahlan-poke78' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to automate the creation and publication of numerous derivative packages, thereby manipulating the npm registry and potentially leading to security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.

How To Fix

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

npm uninstall syahlan-poke78

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 'syahlan-poke78' package and monitor your project's dependencies for any unauthorized changes. Regularly check your package-lock.json file for any unexpected additions or modifications.

Conclusion

The 'syahlan-poke78' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for syahlan-poke78 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate the npm registry by publishing numerous derivative packages.

You can use Vulert to monitor your project for vulnerabilities. Simply upload your package-lock.json file at Vulert Scanner to check for any affected packages.

You should uninstall the package immediately using 'npm uninstall syahlan-poke78' and review your other dependencies for security.

Yes, using compromised packages can lead to security risks, including unauthorized access and data breaches.

There is no patch available for this specific package; the best course of action is to remove it from your project.

How To Fix

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

npm uninstall syahlan-poke78

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