registry / Credential exfiltration / @linjz/opencode-qqbot
@linjz/opencode-qqbot
QQ Bot for OpenCode AI - chat with AI coding assistant via QQ
This report shows the evidence for @linjz/opencode-qqbot@0.3.13. 1 of 13 known versions is blocked or flagged. The newest version, 0.3.14, is allowed. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiStartup discovery sends OPENCODE_PASSWORD to every detected loopback listener before verifying that it is OpenCode. This creates a concrete credential disclosure path to an unrelated local service.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The bot starts with OPENCODE_PASSWORD configured and its OpenCode health check fails, triggering discovery.
Impact
A local listener can capture the OpenCode password, enabling unauthorized access to the OpenCode service.
Mechanism
Discovery enumerates listening ports and sends each an HTTP request containing the password in Basic authorization before validating the /api/info response.
Attack narrative
When OpenCode is unavailable, startup automatically scans local listening ports. Each probe includes OPENCODE_PASSWORD in its Authorization header before the response is checked for an OpenCode signature, so an unrelated local service can receive the credential.
AI rationale
Startup discovery sends OPENCODE_PASSWORD to every detected loopback listener before verifying that it is OpenCode. This creates a concrete credential disclosure path to an unrelated local service.
Evidence
src/core/discovery.tssrc/index.ts
Network endpoints1
127.0.0.1:<detected-port>/api/info
Decision evidence
public snapshotAI called this Malicious at 93.0% confidence as Malware with low false-positive risk.
Evidence for block
- Discovery adds OPENCODE_PASSWORD to an HTTP Basic Authorization header before checking the responding service’s identity.
- The discovery loop sends that request to every detected listening port on 127.0.0.1.
- When OpenCode is unavailable, startup automatically invokes discovery with process.env.OPENCODE_PASSWORD.
Evidence against
- The package is a QQ bot and sends its QQ app credentials to QQ’s token endpoint for normal authentication.
- The discovered URL is loopback and the scan is intended to find a local OpenCode service.
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 High3 Medium5 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
MediumStripped Provenance Metadatasrc/core/discovery.ts
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @linjz/opencode-qqbot@0.3.13.
The versions list below shows the verdict for each recorded version.
- Avoid installing @linjz/opencode-qqbot@0.3.13. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.