registry / @linjz/opencode-qqbot / 0.3.6
@linjz/opencode-qqbot@0.3.6
QQ Bot for OpenCode AI - chat with AI coding assistant via QQ
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package's automatic bot launch is consistent with its stated purpose, and QQ credentials are sent to QQ's official token endpoint. No unrelated collection, concealed execution, or unrequested account action was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The OpenCode plugin starts the configured bot during setup and checks it periodically; credential setup is user initiated.
Impact
No unrelated credential disclosure or unrequested account action was identified.
Mechanism
The bot uses QQ credentials with QQ's token and API services, and connects to the configured OpenCode service. Discovery probes loopback OpenCode endpoints.
AI rationale
The package's automatic bot launch is consistent with its stated purpose, and QQ credentials are sent to QQ's official token endpoint. No unrelated collection, concealed execution, or unrequested account action was found.
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
- There are no install, preinstall, or postinstall hooks; prepublishOnly runs only the two bundle build scripts.
- The plugin reads configured QQ credentials and starts the companion bot when credentials are present, consistent with its QQ bot purpose.
- The bot sends the QQ app ID and secret to QQ's token endpoint at bots.qq.com and uses QQ's official API hosts.
- OpenCode endpoint discovery probes only 127.0.0.1 for the OpenCode /api/info signature.
- The event probe is disabled unless QQ_EVENT_PROBE=true and records event type and session ID, not event content.
Evidence against
- The plugin automatically launches a detached bot and periodically checks whether it needs restarting.
- The bot performs network requests and reads configured credentials as part of connecting to QQ and OpenCode.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
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.6.
See all versions of @linjz/opencode-qqbot for other recorded verdicts.
- Review the evidence and your use of @linjz/opencode-qqbot@0.3.6 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.