sugarchain-bin
The PKGBUILD installs pre-compiled binaries from a GitHub release of a relatively obscure cryptocurrency project (sugarchain), which is a supply-chain concern in itself. The check() function fetches a GPG key from keybase.io at build time via curl piped directly to gpg --import, which is a TOFU (trust on first use) pattern — if keybase.io is compromised or the key is substituted, the verification provides no real protection. The SHA256SUMS.asc file is also fetched at runtime (not in source=() with a pinned hash), meaning its integrity is not guaranteed before use. The binary tarball itself is in source=() with a pinned sha256sum, which is the main protection. However, the overall pattern — executing downloaded pre-built binaries from a niche crypto project, with a GPG verification scheme that can be trivially bypassed by a compromised key host — constitutes a genuine medium-severity supply-chain concern. It is not clearly malicious, but the trust chain is weak.
Triggered rules
external_download_not_in_source
curl/wget fetches a URL on a non-allowlisted host that is not part of source=(), so it is not checksum-verified by makepkg.
-
PKGBUILD:19
curl https://keybase.io/decryp2kanon/pgp_keys.asc | gpg --import
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD installs pre-compiled binaries from a GitHub release of a relatively obscure cryptocurrency project (sugarchain), which is a supply-chain concern in itself. The check() function fetches a GPG key from keybase.io at build time via curl piped directly to gpg --import, which is a TOFU (trust on first use) pattern — if keybase.io is compromised or the key is substituted, the verification provides no real protection. The SHA256SUMS.asc file is also fetched at runtime (not in source=() with a pinned hash), meaning its integrity is not guaranteed before use. The binary tarball itself is in source=() with a pinned sha256sum, which is the main protection. However, the overall pattern — executing downloaded pre-built binaries from a niche crypto project, with a GPG verification scheme that can be trivially bypassed by a compromised key host — constitutes a genuine medium-severity supply-chain concern. It is not clearly malicious, but the trust chain is weak.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Sandelinos
pkgname=sugarchain-bin
pkgver=0.16.3.34_starboy
pkgrel=2
pkgdesc="Sugarchain: one-CPU-one-vote, the world's fastest PoW blockchain"
arch=('x86_64')
url="https://sugarchain.org"
license=('MIT')
depends=('boost' 'boost-libs' 'zeromq' 'libevent')
optdepends=('qt5-base')
_signatures="https://github.com/sugarchain-project/sugarchain/releases/download/v${pkgver//_/-}/SHA256SUMS.asc"
source=("https://github.com/sugarchain-project/sugarchain/releases/download/v${pkgver//_/-}/sugarchain-${pkgver//_/-}-x86_64-linux-gnu.tar.gz")
sha256sums=('4a79d2bb85c306fa37b57ab5790931103e4311b7dc8edeca4c86c3ec26590b62')
check() {
msg 'Validating GPG signature...'
msg2 '(To disable: remove/rename check() function from PKGBUILD)'
curl https://keybase.io/decryp2kanon/pgp_keys.asc | gpg --import
# gpg --recv-key B9DDBDE2AAADC421 # this is Cryptozeny's key
curl -sL $_signatures -o SHA256SUMS.asc
msg2 "Downloading $_signatures"
gpg --verify 'SHA256SUMS.asc'
msg2 'GPG signature is valid.'
msg 'Validating signed checksum of downloaded archive...'
grep "sugarchain-${pkgver//_/-}-x86_64-linux-gnu.tar.gz" 'SHA256SUMS.asc' | tr -d '\r' | sha256sum -c -
msg2 'Checksum valid.'
}
package() {
tar xf "$srcdir/sugarchain-${pkgver//_/-}-x86_64-linux-gnu.tar.gz"
install -Dm644 $srcdir/sugarchain-0.16.3/share/man/man1/* -t $pkgdir/usr/share/man/man1
install -Dm755 $srcdir/sugarchain-0.16.3/bin/* -t $pkgdir/usr/bin
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-09-17 00:27:14 | Medium | 2 |
| 2026-09-16 00:03:17 | Medium | 2 |
| 2026-09-15 00:25:31 | Medium | 2 |
| 2026-09-14 00:27:57 | Medium | 2 |
| 2026-09-13 00:19:54 | Medium | 2 |
| 2026-09-12 00:25:17 | Medium | 2 |
| 2026-09-11 00:19:22 | Medium | 2 |
| 2026-09-10 00:22:44 | Medium | 2 |
| 2026-09-09 00:04:09 | Medium | 2 |
| 2026-09-08 00:18:08 | Medium | 2 |
| 2026-09-07 00:30:15 | Medium | 2 |
| 2026-09-06 00:17:06 | Medium | 2 |
| 2026-09-05 00:16:27 | Medium | 2 |
| 2026-09-04 00:03:13 | Medium | 2 |
| 2026-09-03 00:15:47 | Medium | 2 |
| 2026-09-02 00:02:31 | Medium | 2 |
| 2026-09-01 00:11:19 | Medium | 2 |
| 2026-08-31 00:19:57 | Medium | 2 |
| 2026-08-30 00:04:14 | Medium | 2 |
| 2026-08-29 00:29:17 | Medium | 2 |