concordium-desktop-wallet-bin

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

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary .deb from distribution.mainnet.concordium.software, which is Concordium's own official distribution host (used for their mainnet tooling). The binary is installed and executed directly without any source build. While the host appears to be the legitimate upstream vendor distribution server, installing a prebuilt binary from any external host carries inherent supply-chain risk — if the host or the binary were compromised, arbitrary code would execute on the user's system. The sha512sum provides integrity verification against a known-good hash, which mitigates (but does not eliminate) the risk. There are minor issues: the symlink creation lacks quotes around the path with a space, and the sha512sum appears to be 127 hex chars (should be 128), suggesting a possible truncation. Overall this is a standard 'binary repackage from vendor' pattern common in AUR, rating medium due to the prebuilt binary from an external host rather than source compilation.

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:12 source=("https://distribution.mainnet.concordium.software/tools/linux/concordium-desktop-wallet-$pkgver.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 binary .deb from distribution.mainnet.concordium.software, which is Concordium's own official distribution host (used for their mainnet tooling). The binary is installed and executed directly without any source build. While the host appears to be the legitimate upstream vendor distribution server, installing a prebuilt binary from any external host carries inherent supply-chain risk — if the host or the binary were compromised, arbitrary code would execute on the user's system. The sha512sum provides integrity verification against a known-good hash, which mitigates (but does not eliminate) the risk. There are minor issues: the symlink creation lacks quotes around the path with a space, and the sha512sum appears to be 127 hex chars (should be 128), suggesting a possible truncation. Overall this is a standard 'binary repackage from vendor' pattern common in AUR, rating medium due to the prebuilt binary from an external host rather than source compilation.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Vyacheslav Konovalov <🦀vk@protonmail.com>
    
      2
    
      3pkgname=concordium-desktop-wallet-bin
    
      4pkgver=1.4.1
    
      5pkgrel=1
    
      6pkgdesc='Desktop wallet for Concordium blockchain'
    
      7arch=('x86_64')
    
      8url='https://concordium.com/'
    
      9license=('unknown')
    
      10depends=('gtk3' 'libnotify' 'libsecret' 'libxss' 'nss' 'xdg-utils')
    
      11optional=('libappindicator-gtk3')
    
      12source=("https://distribution.mainnet.concordium.software/tools/linux/concordium-desktop-wallet-$pkgver.deb")
    
      13sha512sums=('3e4317ed2407f04bd965b414519d936d5010b5671c79651f12410f029e2221dce399fd2437528a10cf74e91135f688b60dc03f3cc65281c1b08d4b9f771b1aaa')
    
      14
    
      15prepare() {
    
      16    bsdtar -xf data.tar.xz
    
      17}
    
      18
    
      19package() {
    
      20    cp -r opt usr "$pkgdir"
    
      21    install -d "$pkgdir/usr/bin"
    
      22    ln -s '/opt/Concordium Wallet/concordium-desktop-wallet' "$pkgdir/usr/bin"
    
      23}
    
      24

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