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

syahlan-poke14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166511: Malicious code in syahlan-poke14 (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

The package 'syahlan-poke14' 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 known to flood the npm registry with malicious packages. The primary functionality of such packages is to inflate developer reputation scores through the automatic generation and publication of derivative packages, often with randomized names. This behavior poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'syahlan-poke14' originates from its design to include malicious payloads that modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications of this vulnerability are severe, as it can pollute the npm registry, compromise the integrity of legitimate packages, and potentially expose users to further security risks.

How To Fix

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

npm uninstall syahlan-poke14

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 the 'syahlan-poke14' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'syahlan-poke14' package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for syahlan-poke14 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package.json files and floods the npm registry with derivative packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Using this package can lead to the pollution of the npm registry, compromising the integrity of your application and exposing it to further vulnerabilities.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

Immediately remove the package and update your dependencies to ensure your application is secure.

How To Fix

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

npm uninstall syahlan-poke14

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