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

lina-poke42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158126: Malicious code in lina-poke42 (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-poke42 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 has led to the proliferation of numerous derivative packages designed to manipulate developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability in lina-poke42 stems from its inclusion in a series of malicious packages that automatically generate and publish derivative versions with altered metadata. This includes the removal of private flags in package.json, modification of version numbers, and the creation of random package names. The malicious payload not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall lina-poke42

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 measure, avoid using lina-poke42 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially malicious packages.

Conclusion

The lina-poke42 package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to remove this package and monitor your dependencies closely to maintain security and integrity in your software development practices.

See every vulnerability recorded for lina-poke42 →

Share this vulnerability

FAQ

lina-poke42 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores through the npm registry.

The vulnerability can lead to the injection of malicious code into your project, potentially compromising security and functionality.

You should uninstall the package immediately using the command npm uninstall lina-poke42 and review your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall lina-poke42

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