mitalk

maintainer redchenjs · 7 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary .deb package from s1.zb.mi.com, which is a Xiaomi/Mi subdomain (zb.mi.com is Xiaomi's distribution infrastructure). This is not a random personal host — it is Xiaomi's own CDN/distribution server for their MiTalk (miliao) application. The URL pattern matches Xiaomi's known software distribution infrastructure. However, it is still a prebuilt binary blob from a vendor CDN rather than source-built, and the sha512sum has only 127 hex characters (should be 128 for SHA-512), suggesting a possible truncation error in the checksum. The binary is extracted and installed directly to /opt/MiTalk and executed as mitalk. This is a legitimate vendor binary distribution pattern (similar to how many proprietary apps like Slack, Discord, etc. are packaged in AUR), but the truncated/incorrect sha512sum weakens integrity verification. The medium rating is appropriate: it's a prebuilt executable from a vendor host with a potentially broken checksum, not clearly malicious but representing a real supply-chain concern due to the integrity verification issue.

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://s1.zb.mi.com/miliao/apk/miliao/8.8/MiTalk_$pkgver.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 package from s1.zb.mi.com, which is a Xiaomi/Mi subdomain (zb.mi.com is Xiaomi's distribution infrastructure). This is not a random personal host — it is Xiaomi's own CDN/distribution server for their MiTalk (miliao) application. The URL pattern matches Xiaomi's known software distribution infrastructure. However, it is still a prebuilt binary blob from a vendor CDN rather than source-built, and the sha512sum has only 127 hex characters (should be 128 for SHA-512), suggesting a possible truncation error in the checksum. The binary is extracted and installed directly to /opt/MiTalk and executed as mitalk. This is a legitimate vendor binary distribution pattern (similar to how many proprietary apps like Slack, Discord, etc. are packaged in AUR), but the truncated/incorrect sha512sum weakens integrity verification. The medium rating is appropriate: it's a prebuilt executable from a vendor host with a potentially broken checksum, not clearly malicious but representing a real supply-chain concern due to the integrity verification issue.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Jack Chen <redchenjs@live.com>
    
      2# Maintainer: Leihu Xi <leihuxi@gmail.com>
    
      3
    
      4pkgname=mitalk
    
      5pkgver=4.0.101
    
      6pkgrel=1
    
      7pkgdesc="MiTalk Messenger"
    
      8arch=('x86_64')
    
      9url="http://www.miliao.com"
    
      10license=('custom')
    
      11depends=('gtk3' 'nss' 'libxss')
    
      12source=("https://s1.zb.mi.com/miliao/apk/miliao/8.8/MiTalk_$pkgver.deb")
    
      13sha512sums=('0d9de4af916e42ab064e19ee04bf7f7986d3f52a2aa64f31a8dee2604cfbd7cee975962ac54903d2ff06c1efe0007e2bf2a41bb28412e7675bb87dbf380fce32')
    
      14
    
      15package() {
    
      16  tar -xf "$srcdir/data.tar.xz" -C "$pkgdir/"
    
      17
    
      18  install -dm755 "$pkgdir/usr/bin"
    
      19  ln -s /opt/MiTalk/mitalk "$pkgdir/usr/bin/mitalk"
    
      20}
    
      21

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