youzone

maintainer NeroBlackstone · 1 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged This PKGBUILD fetches a download URL dynamically from the official Yonyou cloud API (yonyoucloud.com/c2.yonyoucloud.com) at build time, then downloads a prebuilt proprietary .deb with no integrity verification (empty source=() and sha256sums=()). The vendor host appears legitimate for this Chinese enterprise software (Yonyou/友空间). There is no obfuscation, no encoded payload, no exfiltration, and no rewriting of upstream sources to attacker-controlled hosts. The real concern is medium-severity: the dynamic URL resolution means the downloaded binary can change at any time without detection, and there are no checksums to verify what was installed. This is a sloppy but not clearly malicious packaging pattern - it's essentially a 'latest version' fetcher with no pinning or integrity checks. The cheaper model's HIGH rating is a false positive; this is a medium risk due to the unverifiable binary download from a vendor CDN with no checksums.

Triggered rules

MEDIUM External download from an untrusted host, not in source=() 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:15 json=$(curl -s 'https://c2.yonyoucloud.com/yonbip-ec-resource/resource/file/get?type=amd64' \

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): This PKGBUILD fetches a download URL dynamically from the official Yonyou cloud API (yonyoucloud.com/c2.yonyoucloud.com) at build time, then downloads a prebuilt proprietary .deb with no integrity verification (empty source=() and sha256sums=()). The vendor host appears legitimate for this Chinese enterprise software (Yonyou/友空间). There is no obfuscation, no encoded payload, no exfiltration, and no rewriting of upstream sources to attacker-controlled hosts. The real concern is medium-severity: the dynamic URL resolution means the downloaded binary can change at any time without detection, and there are no checksums to verify what was installed. This is a sloppy but not clearly malicious packaging pattern - it's essentially a 'latest version' fetcher with no pinning or integrity checks. The cheaper model's HIGH rating is a false positive; this is a medium risk due to the unverifiable binary download from a vendor CDN with no checksums.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Nero Blackstone <gf7600gs@gmail.com>
    
      2
    
      3pkgname=youzone
    
      4pkgver=8.1.0
    
      5pkgrel=1
    
      6pkgdesc="友空间，更懂企业的一体化数智办公平台。Youzone, an integrated digital office platform that better understands enterprises."
    
      7arch=('x86_64')
    
      8url="https://ec.diwork.com/index.html"
    
      9license=('custom:proprietary')
    
      10makedepends=(jq curl)
    
      11source=()
    
      12sha256sums=()
    
      13
    
      14prepare() {
    
      15  json=$(curl -s 'https://c2.yonyoucloud.com/yonbip-ec-resource/resource/file/get?type=amd64' \
    
      16    -H 'sec-ch-ua-platform: "Linux"' \
    
      17    -H 'Referer: https://ec.diwork.com/' \
    
      18    -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36' \
    
      19    -H 'Accept: application/json, text/plain, */*' \
    
      20    -H 'DNT: 1' \
    
      21    -H 'sec-ch-ua-mobile: ?0')
    
      22
    
      23  url=$(echo "$json" | jq -r '.data')
    
      24  curl -L "$url" -o "${srcdir}/${pkgname}.deb"
    
      25
    
      26  bsdtar -xf "${srcdir}/${pkgname}.deb" -C "$srcdir/"
    
      27}
    
      28
    
      29package() {
    
      30  bsdtar -xf "$srcdir"/data.tar.* -C "$pkgdir/"
    
      31}

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