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

syahlan-poke54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166555: Malicious code in syahlan-poke54 (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-poke54' 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. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the creation of numerous derivative packages.

Vulnerability Detail

The vulnerability in 'syahlan-poke54' originates from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious code is designed to exploit the npm infrastructure, potentially affecting other packages and developers relying on the integrity of the registry.

How To Fix

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

npm uninstall syahlan-poke54

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-poke54' and any packages that depend on it. Additionally, you can use the following command to uninstall the package: npm uninstall syahlan-poke54.

Conclusion

The 'syahlan-poke54' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for syahlan-poke54 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of your project and potentially introducing further security risks.

You should uninstall the package immediately using the command: npm uninstall syahlan-poke54.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

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

How To Fix

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

npm uninstall syahlan-poke54

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