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

lina-poke30 Updated 19 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158113: Malicious code in lina-poke30 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

lina-poke30 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of tokens through various npm packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in lina-poke30 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The potential ramifications include unauthorized access to sensitive data and the risk of executing harmful code within applications that depend on this package.

How To Fix

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

npm uninstall lina-poke30

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, avoid using lina-poke30 and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your package dependencies for any updates or vulnerabilities.

Conclusion

The lina-poke30 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for lina-poke30 →

Share this vulnerability

FAQ

lina-poke30 is an npm package that is part of a token reward campaign, but it has been identified as containing malicious code.

The malicious code can modify your package.json file and potentially lead to unauthorized access or execution of harmful code.

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

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to install any software.

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

How To Fix

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

npm uninstall lina-poke30

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