Malicious Code Injection in lina-poke65: A Threat to npm Users

lina-poke65 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158151: Malicious code in lina-poke65 (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-poke65 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 essential files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in lina-poke65 originates from its design to include autopublish scripts that manipulate the package.json file. This manipulation removes private flags, alters version numbers, and generates 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 a degradation of the overall trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall lina-poke65

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-poke65 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The lina-poke65 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects remain secure. Immediate action should be taken to remove this package and monitor for any potential vulnerabilities.

See every vulnerability recorded for lina-poke65 →

Share this vulnerability

FAQ

lina-poke65 is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

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

You should uninstall the package immediately using 'npm uninstall lina-poke65' and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall lina-poke65

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