oicq

maintainer orphaned · 0 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged The PKGBUILD fetches and installs 'oicq@1' directly from the npm registry at build/install time with no pinned integrity hash, no declared source, and no checksum verification. The version specifier 'oicq@1' resolves to the latest 1.x release at the time of installation, meaning the installed code can change between builds without any PKGBUILD update. This is a genuine supply-chain concern: any compromise of the npm package or a version bump within the 1.x range would silently deliver different (potentially malicious) executed JavaScript to users. The source array is empty and noextract references a file that is never actually fetched, making integrity verification impossible. This is a real medium-severity supply-chain risk, not a false positive.

Triggered rules

MEDIUM npm/yarn/pnpm install of an undeclared external package npm_install_external

Runs `npm/yarn/pnpm install <package>` for a package not in source=(), pulling unpinned, unreviewed code at build time. Severity downgraded: the package declares/looks like a Node.js consumer, where build-time installs are expected.

  • PKGBUILD:21 npm i oicq@1 -g \
MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 85%): The PKGBUILD fetches and installs 'oicq@1' directly from the npm registry at build/install time with no pinned integrity hash, no declared source, and no checksum verification. The version specifier 'oicq@1' resolves to the latest 1.x release at the time of installation, meaning the installed code can change between builds without any PKGBUILD update. This is a genuine supply-chain concern: any compromise of the npm package or a version bump within the 1.x range would silently deliver different (potentially malicious) executed JavaScript to users. The source array is empty and noextract references a file that is never actually fetched, making integrity verification impossible. This is a real medium-severity supply-chain risk, not a false positive.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: liolok <aur@liolok.com>
2# Maintainer: Mike Yuan <me@yhndnzj.com>
3
4pkgname=oicq
5pkgver=2.1.9
6pkgrel=1
7pkgdesc="Tecent chat bot in nodejs"
8arch=('any')
9url="https://www.npmjs.com/package/$pkgname"
10license=('MPL-2.0')
11depends=('nodejs')
12makedepends=('npm')
13optdepends=()
14source=()
15
16
17
18noextract=($pkgname-$pkgver.tgz)
19
20package() {
21 npm i oicq@1 -g \
22 --prefix "$pkgdir/usr" \
23 --cache "$srcdir/npm-cache"
24
25 # Non-deterministic race in npm gives 777 permissions to random directories.
26 # See https://github.com/npm/cli/issues/1103 for details.
27 find "${pkgdir}/usr" -type d -exec chmod 755 {} +
28
29# install -dm755 "${pkgdir}/usr/bin"
30
31# cat <<EOF >> "${pkgdir}/usr/bin/oicq"
32# "#!/usr/bin/env node
33# 'use strict';
34# require('/usr/lib/node_modules/oicq/lib')();"
35# EOF
36
37# chmod 755 "${pkgdir}/usr/bin/oicq"
38
39 # npm gives ownership of ALL FILES to build user
40 # https://bugs.archlinux.org/task/63396
41 chown --recursive root:root "${pkgdir}"
42}
43

Scan history

Scanned at (UTC)SeverityRules
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

Report a package

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

0 / 4000
Your suggestion