registry / @linjz/opencode-qqbot / 0.3.5
@linjz/opencode-qqbot@0.3.5
QQ Bot for OpenCode AI - chat with AI coding assistant via QQ
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner's process and network findings correspond to launching the bot and connecting it to QQ and OpenCode. The reviewed lifecycle script only builds bundles, and no unrelated credential collection or transmission was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The bot starts when launched directly or when the configured OpenCode plugin starts and finds no existing bot instance.
Impact
The reviewed flows support the package's stated bot functionality; no unrelated credential transfer or malicious action was found.
Mechanism
The bot authenticates with QQ's API and uses the configured OpenCode endpoint. Discovery probes local loopback ports for the OpenCode service.
AI rationale
The scanner's process and network findings correspond to launching the bot and connecting it to QQ and OpenCode. The reviewed lifecycle script only builds bundles, and no unrelated credential collection or transmission was found.
Evidence
~/.openqq/.env~/.openqq/last-discovered.json~/.openqq/bot.out.log~/.openqq/opencode-events.jsonl
Network endpoints5
bots.qq.com/app/getAppAccessTokenapi.sgroup.qq.comsandbox.api.sgroup.qq.com127.0.0.1:<port>/api/infouser-configured OPENCODE_BASE_URL
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which builds the package bundles.
- The plugin starts the bot when configured with a QQ app ID and no running instance is found.
- QQ app credentials are sent to the QQ Bot token endpoint.
- OpenCode password authentication is attached to requests sent to the configured OpenCode base URL.
- Automatic endpoint discovery probes loopback addresses only.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedbin/openqq.jsView file
6// 注意：本文件必须保持纯 JS（无类型标注）——node 用户直接执行它。
L7: import { spawnSync } from "node:child_process"
L8: import { existsSync } from "node:fs"
High
6Cross-file remote execution chain: bin/openqq.js spawns dist/openqq-bot.js; helper contains network access plus dynamic code execution.
L6: // 注意：本文件必须保持纯 JS（无类型标注）——node 用户直接执行它。
L7: import { spawnSync } from "node:child_process"
L8: import { existsSync } from "node:fs"
...
L17: const candidates = ["bun", "bun.exe", "bun.cmd", "bun.bat"]
L18: if (process.platform === "win32") {
L19: const appdata = process.env.APPDATA || join(process.env.USERPROFILE || "", "AppData", "Roaming")
L20: candidates.push(join(appdata, "npm", "node_modules", "bun", "bin", "bun.exe"))
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
bin/openqq.jsView on unpkg · L6dist/openqq-bot.jsView file
Findings
1 Critical3 High2 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/opencode-qqbot-plugin.js
HighChild Processbin/openqq.js
HighShelldist/openqq-bot.js
HighCross File Remote Execution Contextbin/openqq.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @linjz/opencode-qqbot@0.3.5.
See all versions of @linjz/opencode-qqbot for other recorded verdicts.
- Review the evidence and your use of @linjz/opencode-qqbot@0.3.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.