paup-gui

MEDIUM

maintainer malacology 0 votes scanned 2026-09-17 00:27:14.276658

View on AUR

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-09-17 00:27:14	Medium	2
2026-09-16 00:03:17	Medium	2
2026-09-15 00:25:31	Medium	2
2026-09-14 00:27:57	Medium	2
2026-09-13 00:19:54	Medium	2
2026-09-12 00:25:17	Medium	2
2026-09-11 00:19:22	Medium	2
2026-09-10 00:22:44	Medium	2
2026-09-09 00:04:09	Medium	2
2026-09-08 00:18:08	Medium	2
2026-09-07 00:30:15	Medium	2
2026-09-06 00:17:06	Medium	2
2026-09-05 00:16:27	Medium	2
2026-09-04 00:03:13	Medium	2
2026-09-03 00:15:47	Medium	2
2026-09-02 00:02:31	Medium	2
2026-09-01 00:11:19	Medium	2
2026-08-31 00:19:57	Medium	2
2026-08-30 00:04:14	Medium	2
2026-08-29 00:29:17	Medium	2