Malicious Code Injection in lina-telur52-breki Package

lina-telur52-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74153: Malicious code in lina-telur52-breki (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

The lina-telur52-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. It is particularly vulnerable due to its inclusion of autopublish scripts that modify package metadata and republish variants to the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the lina-telur52-breki package, which includes scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish itself, leading to pollution of the npm registry. The ramifications include potential security risks for developers who inadvertently use this package, as it can compromise their projects and reputations.

How To Fix

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

npm uninstall lina-telur52-breki

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-telur52-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended installations of this package.

Conclusion

The lina-telur52-breki package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with unwanted variants. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for lina-telur52-breki →

Share this vulnerability

FAQ

The lina-telur52-breki package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.

Using the lina-telur52-breki package can lead to security risks, including the potential for your project to be polluted with unwanted packages and compromised reputation.

You should uninstall the lina-telur52-breki package immediately using the command 'npm uninstall lina-telur52-breki' and check your project for any dependencies that may be affected.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the 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-telur52-breki

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