Malicious Code Injection in lina-poke14: A Threat to npm Ecosystem

lina-poke14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158095: Malicious code in lina-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

lina-poke14 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with harmful packages. The primary functionality of lina-poke14 is to serve as a token reward mechanism, but it has been compromised to include malicious scripts that can alter package metadata and publish harmful variants.

Vulnerability Detail

The vulnerability in lina-poke14 originates from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts modify the package.json file to remove private flags, change version numbers, and create random package names, leading to the pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall lina-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 lina-poke14 and any other packages associated with the tea.xyz campaign. Regularly audit your project's dependencies to ensure that no malicious packages are included.

Conclusion

The lina-poke14 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Regular monitoring and auditing of dependencies can help mitigate such risks.

See every vulnerability recorded for lina-poke14 →

Share this vulnerability

FAQ

lina-poke14 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem, specifically related to the tea.xyz token reward initiative.

The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and integrity, as well as pollute the npm registry.

You should uninstall the lina-poke14 package immediately using the command: npm uninstall lina-poke14.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lina-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