sreda
The package downloads a prebuilt binary archive from dl.armgs.team, which is a non-official, third-party host (not the canonical sreda.digital.gov.ru government domain). The entire extracted archive contents are copied wholesale into /opt/sreda with 'cp -a srcdir/.' which installs whatever binaries/libraries are in the tarball. While a sha256sum is present, the trust anchor is only as strong as the host: if dl.armgs.team is compromised or controlled by an unrelated party, the checksum in the PKGBUILD would need to be updated to reflect a malicious payload — but the current checksum does not guarantee the host is trustworthy going forward. The package installs executed native binaries from a non-canonical host for what is described as a Russian government employee communication service, which is a genuine supply-chain concern. This is a real medium-severity issue: prebuilt binaries from an unofficial/personal-team host being installed and executed on the user's system.
Triggered rules
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:18
"${pkgname}-${pkgver}.tar.xz::https://dl.armgs.team/downloads/linux/x64/${pkgver}/${_app_name}"
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The package downloads a prebuilt binary archive from dl.armgs.team, which is a non-official, third-party host (not the canonical sreda.digital.gov.ru government domain). The entire extracted archive contents are copied wholesale into /opt/sreda with 'cp -a srcdir/.' which installs whatever binaries/libraries are in the tarball. While a sha256sum is present, the trust anchor is only as strong as the host: if dl.armgs.team is compromised or controlled by an unrelated party, the checksum in the PKGBUILD would need to be updated to reflect a malicious payload — but the current checksum does not guarantee the host is trustworthy going forward. The package installs executed native binaries from a non-canonical host for what is described as a Russian government employee communication service, which is a genuine supply-chain concern. This is a real medium-severity issue: prebuilt binaries from an unofficial/personal-team host being installed and executed on the user's system.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Yakov P potapovj(at)gmail(dot)com
# Maintainer: KUHTOXO https://aur.archlinux.org/account/kuhtoxo
pkgname=sreda
pkgver=26.1.10.85335
pkgrel=1
pkgdesc="Service for interaction between employees in organizations."
arch=('x86_64')
url="https://sreda.digital.gov.ru/"
license=('proprietary')
options=(!strip)
replaces=('armgs')
_install_path="/opt/${pkgname}"
_archive_name="${pkgname}.tar.xz"
_app_name="${pkgname}.tar.xz"
source=(
"${pkgname}-${pkgver}.tar.xz::https://dl.armgs.team/downloads/linux/x64/${pkgver}/${_app_name}"
"sreda.desktop"
)
sha256sums=('74c29b8bd1b5322d9784c73c221a948f6af30f788649654837c8f18bac0aecc1'
'4cd9a7f70e029a3501af880f4839ad1a52de104ad989e1b0aa1817bfa90675aa')
package() {
mkdir -p "${pkgdir}/opt/${pkgname}"
cp -a "${srcdir}/." "${pkgdir}${_install_path}/"
rm "${pkgdir}${_install_path}/${pkgname}-${pkgver}.tar.xz"
mkdir -p "${pkgdir}/usr/share/applications/"
cp -L "${pkgname}.desktop" "${pkgdir}/usr/share/applications/${pkgname}.desktop"
rm "${pkgdir}/opt/${pkgname}/${pkgname}.desktop"
}
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 |