cryptodredge

maintainer deid84 · 4 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged This PKGBUILD downloads and installs a prebuilt closed-source binary (a cryptocurrency miner) directly from the project's own domain (cryptodredge.org) using a 'latest' URL endpoint rather than a versioned, immutable release artifact. Several concerns: (1) The URL path ends in '/latest' which is a mutable pointer — even though an md5sum is present, md5 is cryptographically broken and trivially collisable, providing weak integrity assurance. (2) The binary is a closed-source, proprietary GPU miner installed directly to /usr/bin with no source code review possible. (3) The license is declared 'none' and the LICENSE.txt installation is commented out, indicating the legal status is unclear. (4) While cryptodredge.org is the legitimate upstream vendor site, it is not an established, widely-audited distribution channel like GitHub releases or a distro mirror. The combination of a mutable 'latest' URL, a broken checksum algorithm (md5), and a closed-source executed binary constitutes a genuine supply-chain risk: if the host is compromised or the 'latest' pointer is updated maliciously, users would receive and execute arbitrary code. This is a real medium-severity 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=("${pkgname}-${pkgver}.tar.gz::https://cryptodredge.org/download/linux/11.4/latest")
MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 78%): This PKGBUILD downloads and installs a prebuilt closed-source binary (a cryptocurrency miner) directly from the project's own domain (cryptodredge.org) using a 'latest' URL endpoint rather than a versioned, immutable release artifact. Several concerns: (1) The URL path ends in '/latest' which is a mutable pointer — even though an md5sum is present, md5 is cryptographically broken and trivially collisable, providing weak integrity assurance. (2) The binary is a closed-source, proprietary GPU miner installed directly to /usr/bin with no source code review possible. (3) The license is declared 'none' and the LICENSE.txt installation is commented out, indicating the legal status is unclear. (4) While cryptodredge.org is the legitimate upstream vendor site, it is not an established, widely-audited distribution channel like GitHub releases or a distro mirror. The combination of a mutable 'latest' URL, a broken checksum algorithm (md5), and a closed-source executed binary constitutes a genuine supply-chain risk: if the host is compromised or the 'latest' pointer is updated maliciously, users would receive and execute arbitrary code. This is a real medium-severity concern, not a false positive.

PKGBUILD

1 offending line(s) highlighted
1pkgname=cryptodredge
2pkgver=0.27.0
3pkgrel=2
4pkgdesc="Simple in use and highly optimized cryptocurrency mining software with stable power consumption. It is designed to take full advantage of your GPU."
5license=('none')
6arch=('x86_64')
7url="https://cryptodredge.org/"
8provides=('cryptodredge')
9conflicts=('cryptodredge')
10replaces=('cryptodredge')
11depends=('cuda')
12source=("${pkgname}-${pkgver}.tar.gz::https://cryptodredge.org/download/linux/11.4/latest")
13options=('!strip')
14
15package() {
16 install -Dm755 CryptoDredge "${pkgdir}/usr/bin/${pkgname}"
17# install -Dm644 LICENSE.txt "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE.txt"
18}
19md5sums=('b70b31e07a651f52e4a3593a1358c6f1')
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