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

syahlan-poke108 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166505: Malicious code in syahlan-poke108 (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-poke108' is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to inflate developer reputation scores through automated publishing of derivative packages. However, this specific package has been compromised to include malicious code that alters its own metadata and behavior.

Vulnerability Detail

The vulnerability in 'syahlan-poke108' originates from its design to include autopublish scripts that modify the package's 'package.json' file. This modification removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised ecosystem where malicious packages can proliferate unchecked.

How To Fix

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

npm uninstall syahlan-poke108

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 'syahlan-poke108' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included. You can also utilize tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The 'syahlan-poke108' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and promotes the proliferation of compromised packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects.

See every vulnerability recorded for syahlan-poke108 →

Share this vulnerability

FAQ

'syahlan-poke108' is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses compromised packages.

You should uninstall 'syahlan-poke108' immediately and check your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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

How To Fix

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

npm uninstall syahlan-poke108

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