lolka-bin

maintainer labaman · 0 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt Electron binary (.deb) from a Yandex Cloud Storage bucket (storage.yandexcloud.net/lolka-electron). While Yandex Cloud is a legitimate cloud provider and this appears to be the vendor's own distribution channel for the Lolka app, it is not a well-known official distribution mirror and the binary is executed directly. The sha256sum provides some integrity protection, but the host is a personal/vendor S3-style bucket that could be silently replaced. The package installs a prebuilt Electron application binary directly into /opt and /usr, which is a real supply-chain concern: if the upstream bucket is compromised or the maintainer changes the binary without updating the checksum in the PKGBUILD, users would execute untrusted code. This is a classic medium-risk pattern — not clearly malicious, but a genuine supply-chain concern due to the unofficial/personal cloud host serving executed binaries.

Triggered rules

MEDIUM source=() URL on a non-standard host source_untrusted_domain

One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).

PKGBUILD:23 source=("${_pkgname}_${pkgver}_amd64.deb::https://storage.yandexcloud.net/lolka-electron/releases/${_pkgname}_${pkgver}_amd64.deb")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt Electron binary (.deb) from a Yandex Cloud Storage bucket (storage.yandexcloud.net/lolka-electron). While Yandex Cloud is a legitimate cloud provider and this appears to be the vendor's own distribution channel for the Lolka app, it is not a well-known official distribution mirror and the binary is executed directly. The sha256sum provides some integrity protection, but the host is a personal/vendor S3-style bucket that could be silently replaced. The package installs a prebuilt Electron application binary directly into /opt and /usr, which is a real supply-chain concern: if the upstream bucket is compromised or the maintainer changes the binary without updating the checksum in the PKGBUILD, users would execute untrusted code. This is a classic medium-risk pattern — not clearly malicious, but a genuine supply-chain concern due to the unofficial/personal cloud host serving executed binaries.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Mikhail Velichko  <efklid@gmail.com>
    
      2# Maintainer: Lolka Team <support@lolka.app>
    
      3
    
      4pkgname=lolka-bin
    
      5pkgver=1.0.100
    
      6pkgrel=1
    
      7#epoch=1
    
      8_pkgname=Lolka
    
      9
    
      10pkgdesc="Lolka - voice chat and screen sharing application"
    
      11arch=("x86_64")
    
      12url="https://lolka.app"
    
      13license=("MIT")
    
      14categories=("network")
    
      15provides=(lolka)
    
      16conflicts=()
    
      17depends=("gtk3" "libnotify" "nss" "libxss" "libxtst" "xdg-utils" "util-linux-libs" "libsecret" "pipewire" "pipewire-pulse")
    
      18
    
      19optdepends=(
    
      20    "libappindicator: for system tray icon" 
    
      21)
    
      22
    
      23source=("${_pkgname}_${pkgver}_amd64.deb::https://storage.yandexcloud.net/lolka-electron/releases/${_pkgname}_${pkgver}_amd64.deb")
    
      24sha256sums=("15c25d3c45314d859db3753764d1b0e6d91d2528c410ef070f502483bdfc9b2c")
    
      25install=${pkgname}.install
    
      26
    
      27prepare() {
    
      28    tar -xf data.tar.xz
    
      29}
    
      30
    
      31build() {
    
      32    :
    
      33}
    
      34
    
      35check() {
    
      36    :
    
      37}
    
      38
    
      39package() {
    
      40    cp -dr --no-preserve=ownership opt usr "${pkgdir}"/
    
      41}
    
      42

Scan history

Scanned at (UTC)	Severity	Rules
2026-08-03 00:08:14	MEDIUM	2
2026-08-02 00:16:08	MEDIUM	2
2026-08-01 00:11:18	MEDIUM	2
2026-07-31 00:14:10	MEDIUM	2
2026-07-30 00:17:23	MEDIUM	2
2026-07-29 00:25:53	MEDIUM	2
2026-07-28 00:07:28	MEDIUM	2
2026-07-27 00:24:32	MEDIUM	2
2026-07-26 00:07:32	MEDIUM	2
2026-07-25 00:13:44	MEDIUM	2
2026-07-24 00:02:28	MEDIUM	2
2026-07-23 00:14:47	MEDIUM	2
2026-07-22 00:29:32	MEDIUM	2
2026-07-21 00:24:15	MEDIUM	2
2026-07-20 00:19:49	MEDIUM	2
2026-07-19 00:17:08	MEDIUM	2
2026-07-18 00:14:48	MEDIUM	2
2026-07-17 00:06:16	MEDIUM	2
2026-07-16 00:05:41	MEDIUM	2
2026-07-15 00:09:25	MEDIUM	2