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

lina-tek5-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74152: Malicious code in lina-tek5-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

lina-tek5-breki is an npm package that is part of a larger ecosystem of packages associated with the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages. Its primary function is to inflate developer reputation scores for token rewards, but this comes at the cost of security and integrity within the npm ecosystem.

Vulnerability Detail

The vulnerability in lina-tek5-breki originates from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The ramifications include compromised developer accounts, loss of trust in the npm ecosystem, and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall lina-tek5-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 remove the lina-tek5-breki package from your project by executing: npm uninstall lina-tek5-breki. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The lina-tek5-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to update or remove this package to protect their applications from potential exploitation. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for lina-tek5-breki →

Share this vulnerability

FAQ

lina-tek5-breki is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your application and potentially exposing it to security risks.

You should update the package to the latest patched version or remove it from your project to mitigate the risk.

Yes, Vulert can monitor your package-lock.json for vulnerabilities in real-time, helping you stay informed about potential threats.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall lina-tek5-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