Malicious Code Injection in lina-poke68: A Threat to npm Packages

lina-poke68 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158154: Malicious code in lina-poke68 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

lina-poke68 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in lina-poke68 stems from its malicious payload that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior is designed to create numerous derivative packages that can mislead users and inflate the reputation of the malicious actors behind the campaign. The origin of this vulnerability is linked to the tea.xyz token reward scheme, which incentivizes the creation of such harmful packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall lina-poke68

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 lina-poke68 package and any other packages that may be associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The lina-poke68 package poses a significant security risk due to its malicious code that alters package files and republish variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for lina-poke68 →

Share this vulnerability

FAQ

lina-poke68 is an npm package identified as part of a malicious campaign that modifies package files and republish variants to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately using npm uninstall lina-poke68 and check your project for any other affected packages.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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 lina-poke68

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