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

syahlan-poke83 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166587: Malicious code in syahlan-poke83 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

syahlan-poke83 is a package within the npm ecosystem, which is commonly used for JavaScript development. It is part of a broader campaign that exploits npm's package management system to inflate developer reputation scores through the generation of numerous derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry by publishing malicious variants that can compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in syahlan-poke83 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly install these compromised packages. The ramifications include loss of trust in the npm ecosystem, potential data breaches, and the risk of executing malicious code in applications that depend on these packages.

How To Fix

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

npm uninstall syahlan-poke83

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-poke83 and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit or Vulert to identify and mitigate vulnerabilities in your project.

Conclusion

The syahlan-poke83 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to be vigilant and remove any affected packages from their projects. Regular audits and monitoring can help maintain the integrity of your applications.

See every vulnerability recorded for syahlan-poke83 →

Share this vulnerability

FAQ

syahlan-poke83 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your application's dependencies, potentially compromising its security and integrity.

If you have installed syahlan-poke83, you should uninstall it immediately and check your package-lock.json file for any references to this package.

You can use tools like npm audit or Vulert to monitor your npm packages for vulnerabilities. Vulert allows you to check your application for vulnerabilities in real-time using just your 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.

How To Fix

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

npm uninstall syahlan-poke83

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