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

lina-poke70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158157: Malicious code in lina-poke70 (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

lina-poke70 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. It is designed to facilitate the distribution of rewards through various npm packages. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish numerous derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in lina-poke70 stems from its inclusion in a malicious campaign that employs scripts to modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches or unintended consequences in their applications.

How To Fix

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

npm uninstall lina-poke70

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-poke70 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The lina-poke70 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for lina-poke70 →

Share this vulnerability

FAQ

lina-poke70 is an npm package involved in a token reward campaign that has been identified as malicious.

The vulnerability can lead to the injection of malicious code, which may compromise your application's security and integrity.

You should remove the lina-poke70 package from your project immediately and monitor for any updates or patches.

Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

Vulert is a tool that monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json, ensuring your software remains secure.

How To Fix

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

npm uninstall lina-poke70

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