xvolkolak

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

MEDIUM

Why flagged The package downloads a prebuilt binary tarball (an unpacker emulator tool) from libpcap.net, which is the maintainer's personal domain rather than the official upstream release host (which is commented out as a Dropbox URL). The comment even acknowledges the official source is the Dropbox link and that the libpcap.net mirror was set up by the maintainer via wget mirroring. This is a classic supply-chain concern: a prebuilt executable is being served from a personal server controlled by the package maintainer, not the upstream author. If the maintainer's server were compromised or the maintainer acted maliciously, a different binary could be substituted. The sha256sum provides some protection against silent substitution but not against the maintainer intentionally serving a malicious binary. The 'base' directory likely contains native binaries (it's an unpacker emulator), and shell scripts are installed to /usr/bin. This is a genuine medium-severity supply-chain concern: executed binaries from a non-official personal host.

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:14 source=("http://libpcap.net/xvolkolak/xvlk_lin64_public_${pkgver}.tar.gz")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 75%): The package downloads a prebuilt binary tarball (an unpacker emulator tool) from libpcap.net, which is the maintainer's personal domain rather than the official upstream release host (which is commented out as a Dropbox URL). The comment even acknowledges the official source is the Dropbox link and that the libpcap.net mirror was set up by the maintainer via wget mirroring. This is a classic supply-chain concern: a prebuilt executable is being served from a personal server controlled by the package maintainer, not the upstream author. If the maintainer's server were compromised or the maintainer acted maliciously, a different binary could be substituted. The sha256sum provides some protection against silent substitution but not against the maintainer intentionally serving a malicious binary. The 'base' directory likely contains native binaries (it's an unpacker emulator), and shell scripts are installed to /usr/bin. This is a genuine medium-severity supply-chain concern: executed binaries from a non-official personal host.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Tony Lambiris <tony@libpcap.net>
    
      2
    
      3pkgname=xvolkolak
    
      4pkgver=0.22
    
      5pkgrel=3
    
      6pkgdesc="Xvolkolak is an unpacker emulator"
    
      7arch=(x86_64)
    
      8url="http://n10info.blogspot.com/"
    
      9license=(custom)
    
      10depends=(glibc)
    
      11# official source below
    
      12#source=('https://www.dropbox.com/s/7sk61nc798kcg32/xvlk_lin64_public_0.22.tar.gz?dl=1')
    
      13# wget --mirror --no-parent --convert-links --directory-prefix=xvolkolak --html-extension --restrict-file-names=windows http://n10info.blogspot.com/2018/08/xvolkolak-022.html
    
      14source=("http://libpcap.net/xvolkolak/xvlk_lin64_public_${pkgver}.tar.gz")
    
      15install="$pkgname.install"
    
      16sha256sums=('4b77ce5eab33314b13b7982cffdd7526b7a8f3575945ad13aae3ec1a79d95035')
    
      17
    
      18package() {
    
      19	mkdir -p "$pkgdir/usr/share/xvolkolak" "$pkgdir/usr/bin"
    
      20
    
      21	cp -a "${srcdir}/xvlk_lin64_public/base" "$pkgdir/usr/share/xvolkolak/"
    
      22	cp -a "${srcdir}/xvlk_lin64_public/xvlkc.sh" \
    
      23		"${srcdir}/xvlk_lin64_public/xvlk.sh" "$pkgdir/usr/bin/"
    
      24	sed -i -re 's|./base|/usr/share/xvolkolak/base|g' "${pkgdir}"/usr/bin/*.sh
    
      25}
    
      26

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