quartz-messenger

MEDIUM
maintainer kleintux 0 votes scanned 2026-11-01 00:21:48.120785
View on AUR
Why flagged

The PKGBUILD downloads a source tarball from a personal/unofficial GitLab-like instance (bultek.synchron.com.ua) using curl with -k (SSL verification disabled), bypassing the source=() array and thus all checksum verification. The commented-out source= line with md5sums='SKIP' shows the maintainer was aware of the proper mechanism but chose to use curl instead. The -k flag disabling TLS certificate verification makes this susceptible to MITM attacks in addition to the supply-chain risk from an unofficial host. The downloaded tarball is then compiled with cargo and the resulting binary is installed to /usr/bin. This is a genuine medium-severity supply-chain concern: executed/compiled code from an unofficial host with no integrity verification and TLS disabled.

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:19 curl -k -LO "http://bultek.synchron.com.ua/bultekdev/software/quartz-messenger/-/archive/${_pkgver}/quartz-messenger-${_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 82%): The PKGBUILD downloads a source tarball from a personal/unofficial GitLab-like instance (bultek.synchron.com.ua) using curl with -k (SSL verification disabled), bypassing the source=() array and thus all checksum verification. The commented-out source= line with md5sums='SKIP' shows the maintainer was aware of the proper mechanism but chose to use curl instead. The -k flag disabling TLS certificate verification makes this susceptible to MITM attacks in addition to the supply-chain risk from an unofficial host. The downloaded tarball is then compiled with cargo and the resulting binary is installed to /usr/bin. This is a genuine medium-severity supply-chain concern: executed/compiled code from an unofficial host with no integrity verification and TLS disabled.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: kleintux <reg-archlinux AT klein DOT tuxli DOT ch>
2# Contributor: Demir Yerli <mrquantumoff@protonmail.com>
3pkgname=quartz-messenger
4pkgver=0.3.0
5_pkgver=v${pkgver}
6pkgrel=1
7pkgdesc="libquartz based messenger"
8arch=(x86_64)
9url="http://bultek.synchron.com.ua/bultekdev/software/quartz-messenger"
10license=('MIT')
11groups=("mrquantumoff")
12depends=("openssl")
13makedepends=('git' 'cargo' 'rust')
14#source=("http://bultek.synchron.com.ua/bultekdev/software/quartz-messenger/-/archive/${_pkgver}/quartz-messenger-${_pkgver}.tar.gz")
15#md5sums=('SKIP')
16
17prepare() {
18 cd ${srcdir}
19 curl -k -LO "http://bultek.synchron.com.ua/bultekdev/software/quartz-messenger/-/archive/${_pkgver}/quartz-messenger-${_pkgver}.tar.gz"
20 tar -xpf quartz-messenger-${_pkgver}.tar.gz
21}
22
23build(){
24 cd ${srcdir}/quartz-messenger-${_pkgver}
25 cargo build -r
26}
27
28package() {
29 cd "${srcdir}/quartz-messenger-${_pkgver}"
30 install -Dm755 -t "${pkgdir}/usr/bin/" target/release/quartz-messenger
31 chmod +x ${pkgdir}/usr/bin/quartz-messenger
32 install -Dm644 "LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
33 install -Dm644 "README.md" "${pkgdir}/usr/share/doc/${pkgname}/README.md"
34}
35

Scan history

Scanned at (UTC)SeverityRules
2026-11-01 00:21:48 Medium 2
2026-10-31 00:07:41 Medium 2
2026-10-30 00:29:30 Medium 2
2026-10-29 00:13:55 Medium 2
2026-10-28 00:06:54 Medium 2
2026-10-27 00:23:28 Medium 2
2026-10-26 00:12:40 Medium 2
2026-10-25 00:20:48 Medium 2
2026-10-24 00:14:55 Medium 2
2026-10-23 00:02:19 Medium 2
2026-10-22 00:13:10 Medium 2
2026-10-21 00:12:50 Medium 2
2026-10-20 00:10:31 Medium 2
2026-10-19 00:03:55 Medium 2
2026-10-18 00:06:55 Medium 2
2026-10-17 00:21:55 Medium 2
2026-10-16 00:12:47 Medium 2
2026-10-15 00:28:05 Medium 2
2026-10-14 00:06:47 Medium 2
2026-10-13 00:23:45 Medium 2

Report a package

Reports go to the AURWatch maintainer (one person) and are read by hand. No login required.

0 / 4000
Your suggestion