paup-gui

maintainer malacology · 0 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged This PKGBUILD downloads a prebuilt MSI installer from phylosolutions.com (the official upstream vendor site for PAUP, a legitimate phylogenetics software package), so the host itself is not suspicious. However, there are two real concerns: (1) md5sums=('SKIP') means there is no integrity verification whatsoever — any MITM or server compromise would silently deliver a different binary; (2) the package() function runs 'wine msiexec /i ...' which executes the MSI installer interactively during the build phase rather than extracting files to $pkgdir, meaning it installs into the user's Wine prefix rather than the Arch package tree — this is both broken packaging practice and a code-execution concern since an unverified binary is directly executed. The combination of no checksum and direct execution of a downloaded binary from an external host (even a legitimate one) constitutes a real supply-chain risk. The broken packaging pattern (installing to Wine prefix instead of $pkgdir) also means the package cannot be properly tracked or uninstalled by pacman.

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:16 source=("http://phylosolutions.com/paup-test/paup4-setup.msi")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 85%): This PKGBUILD downloads a prebuilt MSI installer from phylosolutions.com (the official upstream vendor site for PAUP, a legitimate phylogenetics software package), so the host itself is not suspicious. However, there are two real concerns: (1) md5sums=('SKIP') means there is no integrity verification whatsoever — any MITM or server compromise would silently deliver a different binary; (2) the package() function runs 'wine msiexec /i ...' which executes the MSI installer interactively during the build phase rather than extracting files to $pkgdir, meaning it installs into the user's Wine prefix rather than the Arch package tree — this is both broken packaging practice and a code-execution concern since an unverified binary is directly executed. The combination of no checksum and direct execution of a downloaded binary from an external host (even a legitimate one) constitutes a real supply-chain risk. The broken packaging pattern (installing to Wine prefix instead of $pkgdir) also means the package cannot be properly tracked or uninstalled by pacman.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: malacology
    
      2# Contributor: malacology
    
      3
    
      4pkgname=paup-gui
    
      5pkgver=4.0a
    
      6pkgrel=1
    
      7pkgdesc="Phylogenetic Analysis Using PAUP"
    
      8arch=('any')
    
      9url="http://phylosolutions.com/paup-test/"
    
      10license=('custom')
    
      11depends=(
    
      12	'wine'
    
      13	'wine_gecko'
    
      14	'wine-mono'
    
      15)
    
      16source=("http://phylosolutions.com/paup-test/paup4-setup.msi")
    
      17md5sums=('SKIP')
    
      18
    
      19package() {
    
      20
    
      21  wine msiexec /i "$srcdir"/paup4-setup.msi
    
      22}
    
      23

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