elephantdrive

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

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary .deb from 'distribution.vaultservices.net', which is not the official elephantdrive.com domain but appears to be a vendor-controlled distribution subdomain (vaultservices.net is associated with ElephantDrive's parent/infrastructure). The binary is executed directly after extraction. While sha256sums are present providing integrity verification against tampering in transit, the host is not the canonical upstream URL listed in the 'url' field (elephantdrive.com), and there is no GPG signature verification. A prebuilt closed-source binary installed to /usr/bin from a non-primary vendor domain with only a checksum (no signature) represents a real supply-chain concern: if the distribution host is compromised or the checksum is updated to match a malicious binary, arbitrary code would execute with system privileges. This is a genuine medium-severity supply-chain risk, not a false positive.

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 "http://distribution.vaultservices.net/edNative/out/debian/elephantdrive_${pkgver}_amd64.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 from 'distribution.vaultservices.net', which is not the official elephantdrive.com domain but appears to be a vendor-controlled distribution subdomain (vaultservices.net is associated with ElephantDrive's parent/infrastructure). The binary is executed directly after extraction. While sha256sums are present providing integrity verification against tampering in transit, the host is not the canonical upstream URL listed in the 'url' field (elephantdrive.com), and there is no GPG signature verification. A prebuilt closed-source binary installed to /usr/bin from a non-primary vendor domain with only a checksum (no signature) represents a real supply-chain concern: if the distribution host is compromised or the checksum is updated to match a malicious binary, arbitrary code would execute with system privileges. This is a genuine medium-severity supply-chain risk, not a false positive.

PKGBUILD

1 offending line(s) highlighted

      1# Contributor: Ben Alex <ben.alex@acegi.com.au>
    
      2# Maintainer: Ben Alex <ben.alex@acegi.com.au>
    
      3
    
      4pkgname=elephantdrive
    
      5pkgver=3.8.3
    
      6pkgrel=1
    
      7pkgdesc='Service for the Elephant Drive encrypted cloud backup service'
    
      8arch=('x86_64')
    
      9url="http://www.elephantdrive.com"
    
      10license=('custom')
    
      11backup=('etc/elephantdrive.config')
    
      12
    
      13source=('elephantdrive.service'
    
      14        "http://distribution.vaultservices.net/edNative/out/debian/elephantdrive_${pkgver}_amd64.deb")
    
      15noextract=("elephantdrive_${pkgver}_amd64.deb")
    
      16sha256sums=('06f9908b0086fd65ef022f764a6c10833dbc39f72c40e6290f2edc2cfc37fb86'
    
      17            '50ca532ec9c720fb88286b1d987ae2a737c0f8cc54d18a090944e0a8de292062')
    
      18
    
      19package() {
    
      20	ar xf "elephantdrive_${pkgver}_amd64.deb"
    
      21	tar xf data.tar.xz -C "${srcdir}"
    
      22	install -Dm755 ${srcdir}/usr/sbin/elephantdrive ${pkgdir}/usr/bin/elephantdrive
    
      23	install -Dm600 ${srcdir}/etc/elephantdrive.config ${pkgdir}/etc/elephantdrive.config
    
      24	install -Dm644 ${srcdir}/elephantdrive.service ${pkgdir}/usr/lib/systemd/system/elephantdrive.service
    
      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