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

lina-poke67 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158153: Malicious code in lina-poke67 (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-poke67 is an npm package that appears to be part of a broader campaign aimed at exploiting the npm registry. This package, like others in the tea.xyz token reward scheme, is designed to manipulate developer reputation scores by flooding the registry with derivative packages. Its primary function is to generate and publish these packages automatically, which can lead to significant pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in lina-poke67 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a scheme to inflate developer reputation scores for token rewards, leading to a polluted npm registry filled with potentially harmful packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been identified as a source of numerous malicious packages on npm.

How To Fix

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

npm uninstall lina-poke67

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-poke67 package and monitor your package-lock.json for any unauthorized changes. If you suspect that your project has been affected, consider using tools like Vulert to scan your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lina-poke67 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores. It is crucial to remove this package and monitor your project for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for lina-poke67 →

Share this vulnerability

FAQ

lina-poke67 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially allowing malicious code to be executed and polluting your project with harmful dependencies.

You should uninstall the lina-poke67 package immediately using the command npm uninstall lina-poke67 and review your project's dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.

There are no patches available for lina-poke67 as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall lina-poke67

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