chromiumos-snapshot-bin
Two real concerns here: (1) A prebuilt binary archive is downloaded from download-chromium.appspot.com with sha256sums=('SKIP'), meaning no integrity verification. While download-chromium.appspot.com is a Google-operated service that serves Chromium snapshots, the lack of checksum means any MITM or server-side substitution would go undetected. (2) The package hardcodes real Google API credentials (GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID, GOOGLE_DEFAULT_CLIENT_SECRET) in a world-readable shell script — these are the well-known public Chromium build keys, not a secret exfiltration, but worth noting. The primary concern remains the SKIP'd checksum on an executed binary: even from a legitimate host, this is a genuine supply-chain risk since the binary is executed directly on the user's system. The host itself (appspot.com/Google) is semi-official for Chromium snapshots, which keeps this from being high severity, but the missing integrity check on an executed binary warrants medium.
Triggered rules
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:11
source=("chromiumos.zip::https://download-chromium.appspot.com/dl/Linux_ChromiumOS_Full?type=snapshots")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): Two real concerns here: (1) A prebuilt binary archive is downloaded from download-chromium.appspot.com with sha256sums=('SKIP'), meaning no integrity verification. While download-chromium.appspot.com is a Google-operated service that serves Chromium snapshots, the lack of checksum means any MITM or server-side substitution would go undetected. (2) The package hardcodes real Google API credentials (GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID, GOOGLE_DEFAULT_CLIENT_SECRET) in a world-readable shell script — these are the well-known public Chromium build keys, not a secret exfiltration, but worth noting. The primary concern remains the SKIP'd checksum on an executed binary: even from a legitimate host, this is a genuine supply-chain risk since the binary is executed directly on the user's system. The host itself (appspot.com/Google) is semi-official for Chromium snapshots, which keeps this from being high severity, but the missing integrity check on an executed binary warrants medium.
PKGBUILD
1 offending line(s) highlightedpkgname=chromiumos-snapshot-bin
pkgver=1
pkgrel=1
pkgdesc="ChromiumOS compiled for Linux and can run ChromeOS kiosk enterprise apps"
pkgbase=pkgbase
arch=('x86_64')
url="https://download-chromium.appspot.com/"
license=('BSD')
depends=('glibc')
makedepends=('unzip')
source=("chromiumos.zip::https://download-chromium.appspot.com/dl/Linux_ChromiumOS_Full?type=snapshots")
sha256sums=('SKIP')
build() {
:
}
package() {
install -d "$pkgdir/usr/bin/chrome"
unzip "$srcdir/chromiumos.zip" -d "$srcdir"
cp -r "$srcdir/chrome-chromeos/"* "$pkgdir/usr/bin/chrome/"
install -d "$pkgdir/usr/bin"
cat << 'EOF' > "$pkgdir/usr/bin/chromiumos"
#!/bin/bash
export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k"
export GOOGLE_DEFAULT_CLIENT_ID="77185425430.apps.googleusercontent.com"
export GOOGLE_DEFAULT_CLIENT_SECRET="OTJgUOQcT7lO7GsGZq2G4IlT"
/usr/bin/chrome/chrome --login-manager
EOF
chmod +x "$pkgdir/usr/bin/chromiumos"
install -d "$pkgdir/usr/share/applications"
cat << EOF > "$pkgdir/usr/share/applications/chromiumos.desktop"
[Desktop Entry]
Type=Application
Name=ChromiumOS
Exec=/usr/bin/chromiumos
Icon=/usr/bin/chrome/product_logo_48.png
Terminal=false
Categories=Network;WebBrowser;
EOF
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-11-01 00:21:48 | Medium | 2 |
| 2026-10-31 00:07:41 | Medium | 2 |
| 2026-10-30 00:29:30 | Medium | 2 |
| 2026-10-29 00:13:55 | Medium | 2 |
| 2026-10-28 00:06:54 | Medium | 2 |
| 2026-10-27 00:23:28 | Medium | 2 |
| 2026-10-26 00:12:40 | Medium | 2 |
| 2026-10-25 00:20:48 | Medium | 2 |
| 2026-10-24 00:14:55 | Medium | 2 |
| 2026-10-23 00:02:19 | Medium | 2 |
| 2026-10-22 00:13:10 | Medium | 2 |
| 2026-10-21 00:12:50 | Medium | 2 |
| 2026-10-20 00:10:31 | Medium | 2 |
| 2026-10-19 00:03:55 | Medium | 2 |
| 2026-10-18 00:06:55 | Medium | 2 |
| 2026-10-17 00:21:55 | Medium | 2 |
| 2026-10-16 00:12:47 | Medium | 2 |
| 2026-10-15 00:28:05 | Medium | 2 |
| 2026-10-14 00:06:47 | Medium | 2 |
| 2026-10-13 00:23:45 | Medium | 2 |