Malicious Code Injection in syahlan-poke13: A Threat to npm Users

syahlan-poke13 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166510: Malicious code in syahlan-poke13 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

syahlan-poke13 is an npm package that appears to be part of a broader malicious campaign targeting the npm registry. This package is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards associated with the tea.xyz protocol. The package's functionality is compromised due to its malicious intent, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in syahlan-poke13 stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also undermines the trustworthiness of the ecosystem, potentially exposing users to further security risks and dependency issues.

How To Fix

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

npm uninstall syahlan-poke13

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, users can avoid using syahlan-poke13 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The syahlan-poke13 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. Users are urged to remove this package and monitor their projects for vulnerabilities using tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for syahlan-poke13 →

Share this vulnerability

FAQ

syahlan-poke13 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks and dependency issues.

You should immediately remove the syahlan-poke13 package from your project and monitor for any updates or patches.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall syahlan-poke13

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