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

lina-poke32 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158115: Malicious code in lina-poke32 (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-poke32 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the ecosystem but has been compromised, leading to significant security concerns. The package's primary attributes include its ability to integrate with various npm functionalities, but its recent malicious modifications have raised alarms about its integrity and safety.

Vulnerability Detail

The vulnerability in lina-poke32 stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to reputation inflation for developers involved in the tea protocol token rewards. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall lina-poke32

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 remove the lina-poke32 package from your project by executing the command: 'npm uninstall lina-poke32'. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.

Conclusion

The lina-poke32 package has been identified as containing malicious code that poses a significant risk to developers using npm. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for lina-poke32 →

Share this vulnerability

FAQ

lina-poke32 is an npm package that is part of the tea.xyz token reward campaign, designed to facilitate certain functionalities within the npm ecosystem.

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

You should immediately uninstall the package and monitor your project for any unusual behavior. Consider updating to a patched version if available.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.

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-poke32

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