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

lina-poke46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158130: Malicious code in lina-poke46 (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-poke46 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the tea.xyz token reward scheme, is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages with the intent to inflate developer reputation scores. Its functionality is compromised by the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in lina-poke46 stems from its inclusion in a malicious campaign that deploys scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install 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-poke46

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 the lina-poke46 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.

Conclusion

The lina-poke46 package poses a significant threat due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package from any projects.

See every vulnerability recorded for lina-poke46 →

Share this vulnerability

FAQ

lina-poke46 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of compromised packages, which may expose your project to further security risks and instability.

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

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.

Yes, consider using other reputable npm packages that offer similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall lina-poke46

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