registry / @linjz/opencode-qqbot / 0.3.11
@linjz/opencode-qqbot@0.3.11
QQ Bot for OpenCode AI - chat with AI coding assistant via QQ
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged execution and network behavior serves the bot’s runtime: it launches its entry point, uses QQ credentials with QQ’s official API, and discovers a local OpenCode endpoint. The install lifecycle script only builds bundles, and the reviewed journal write is local.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; plugin setup may launch the bot when configured.
Impact
No malicious impact is evident in the inspected source.
Mechanism
The bot uses QQ credentials with QQ’s token service, connects to the configured OpenCode service, and performs local endpoint discovery and journaling.
AI rationale
The flagged execution and network behavior serves the bot’s runtime: it launches its entry point, uses QQ credentials with QQ’s official API, and discovers a local OpenCode endpoint. The install lifecycle script only builds bundles, and the reviewed journal write is local.
Evidence
~/.openqq/inflight.json
Network endpoints4
bots.qq.com/app/getAppAccessTokenapi.sgroup.qq.comsandbox.api.sgroup.qq.com127.0.0.1:<port>/api/info
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which builds the bundles.
- The CLI runs the package’s bot entry point when invoked.
- QQ app credentials are sent to QQ’s official token endpoint.
- OpenCode discovery runs fixed local port-listing commands and probes loopback endpoints.
- The in-flight journal stores message records locally with restrictive file permissions.
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.11.
See all versions of @linjz/opencode-qqbot for other recorded verdicts.
- Review the evidence and your use of @linjz/opencode-qqbot@0.3.11 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.