concordium-mainnet-node-bin

maintainer orphaned · 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 infrastructure (concordium.software is the project's primary domain). This is analogous to downloading from a vendor's own CDN/distribution server rather than GitHub releases, so it is not a random personal host. However, it is still a prebuilt binary being extracted and installed directly, with no source build, and the host is not a widely-recognized code hosting platform. The sha512sums are present and pin the binary, which mitigates substitution risk significantly. The main residual concern is that if Concordium's distribution server were compromised, the binary could be replaced (though the hash check would catch that for this specific version). Overall this is a legitimate vendor binary with hash verification — the pattern is common for blockchain node software distributed as .deb packages. The cheaper model's MEDIUM rating is a marginal false positive given the official vendor domain and hash pinning, but the prebuilt binary nature keeps it from being fully clean.

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 "https://distribution.mainnet.concordium.software/deb/concordium-mainnet-node_${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 binary .deb from distribution.mainnet.concordium.software, which is Concordium's own official distribution infrastructure (concordium.software is the project's primary domain). This is analogous to downloading from a vendor's own CDN/distribution server rather than GitHub releases, so it is not a random personal host. However, it is still a prebuilt binary being extracted and installed directly, with no source build, and the host is not a widely-recognized code hosting platform. The sha512sums are present and pin the binary, which mitigates substitution risk significantly. The main residual concern is that if Concordium's distribution server were compromised, the binary could be replaced (though the hash check would catch that for this specific version). Overall this is a legitimate vendor binary with hash verification — the pattern is common for blockchain node software distributed as .deb packages. The cheaper model's MEDIUM rating is a marginal false positive given the official vendor domain and hash pinning, but the prebuilt binary nature keeps it from being fully clean.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Vyacheslav Konovalov <🦀vk@protonmail.com>
    
      2
    
      3pkgname=concordium-mainnet-node-bin
    
      4pkgver=4.1.1
    
      5pkgrel=1
    
      6pkgdesc='Concordium Mainnet Node'
    
      7arch=('x86_64')
    
      8url='http://developer.concordium.software/en/mainnet/net/index.html'
    
      9license=('AGPL3')
    
      10depends=('postgresql-libs' 'openssl' 'unbound')
    
      11source=(
    
      12    "https://distribution.mainnet.concordium.software/deb/concordium-mainnet-node_${pkgver}_amd64.deb"
    
      13    'concordium-mainnet-node.default'
    
      14    'concordium-mainnet-node-collector.default'
    
      15)
    
      16sha512sums=(
    
      17    '2932594fc2e8ea7361e00bba541485240e42d1656b1b8ac7593ca02b1b191268b58180a86f9a9af2ce93616320685afa916419a8c616cae99eb33ad098cd14fb'
    
      18    'b1d37f98eb7647de17b068ae58b217850d9382680534adad9921de111f6d8078b9121924fc539791d50eb4198280e3b3b71318ba7aa4fee7b79d556326ac7661'
    
      19    '1d89a0c782f0f5e2ce8543e20bc32cd0382cdc7e5fb2be7bddf47393810073c7fc00553c1abcc9103f0851065c355920bba8c59ea7a5080dde68ca4c79fce0b3'
    
      20)
    
      21options=(!strip)
    
      22install='concordium-mainnet-node.install'
    
      23backup=(
    
      24    'etc/default/concordium-mainnet-node'
    
      25    'etc/default/concordium-mainnet-node-collector'
    
      26)
    
      27
    
      28prepare() {
    
      29    tar -xf data.tar.xz
    
      30    rm -rf usr/share
    
      31    mv lib usr
    
      32
    
      33    sed -i '/^ExecStart/i EnvironmentFile=\/etc\/default\/concordium-mainnet-node' \
    
      34        usr/lib/systemd/system/concordium-mainnet-node.service
    
      35    sed -i '/^ExecStart/i EnvironmentFile=\/etc\/default\/concordium-mainnet-node-collector' \
    
      36        usr/lib/systemd/system/concordium-mainnet-node-collector.service
    
      37}
    
      38
    
      39package() {
    
      40    cp -r usr var "$pkgdir/"
    
      41    install -Dm644 concordium-mainnet-node.default "$pkgdir/etc/default/concordium-mainnet-node"
    
      42    install -Dm644 concordium-mainnet-node-collector.default "$pkgdir/etc/default/concordium-mainnet-node-collector"
    
      43}
    
      44

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