concordium-node-bin

maintainer charlottedurand · 0 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged The PKGBUILD downloads a prebuilt binary .deb from distribution.mainnet.concordium.software, which is the official Concordium project's distribution infrastructure (not a personal or unofficial host). The sha256sum is pinned, which mitigates MITM risk. However, this is still a prebuilt binary from a non-GitHub source (not the upstream GitHub releases page), and the binary is executed directly on the user's system. The domain is plausibly official Concordium infrastructure, but it is not a well-known, widely-audited distribution channel. The medium rating is appropriate: pinned hash reduces but does not eliminate supply-chain risk (the hash could have been set when the host was already compromised), and the package installs an executed binary from a non-standard host. This is a legitimate medium concern, not a false positive.

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/deb/concordium-node_${pkgver}-mainnet_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 the official Concordium project's distribution infrastructure (not a personal or unofficial host). The sha256sum is pinned, which mitigates MITM risk. However, this is still a prebuilt binary from a non-GitHub source (not the upstream GitHub releases page), and the binary is executed directly on the user's system. The domain is plausibly official Concordium infrastructure, but it is not a well-known, widely-audited distribution channel. The medium rating is appropriate: pinned hash reduces but does not eliminate supply-chain risk (the hash could have been set when the host was already compromised), and the package installs an executed binary from a non-standard host. This is a legitimate medium concern, not a false positive.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Martoko <mbastholm at gmail dot com>
2
3pkgname=concordium-node-bin
4pkgver=1.0.1
5pkgrel=1
6pkgdesc="Node for the Concordium blockchain"
7arch=('x86_64')
8url="https://github.com/Concordium/concordium-node"
9license=('AGPL3')
10depends=('postgresql-libs' 'openssl' 'unbound')
11install=concordium-node-bin.install
12source=("https://distribution.mainnet.concordium.software/deb/concordium-node_${pkgver}-mainnet_amd64.deb")
13sha256sums=('dcb76543e4fb0346242df1d8873bbdf89af6ccbd49ea6b4d315bd1dc4c14a135')
14
15package() {
16 tar xf data.tar.xz -C "${pkgdir}"
17 rm -r "${pkgdir}/usr/share" # Delete changelog.Debian.gz
18 mv "${pkgdir}/lib" "${pkgdir}/usr"
19}
20

Scan history

Scanned at (UTC)SeverityRules
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

Report a package

Reports go to the AURWatch maintainer (one person) and are read by hand. No login required.

0 / 4000
Your suggestion