registry / AI-agent control-surface risk / opencode-mission
opencode-mission
OpenCode plugin that enables autonomous mission-driven agent mode with 4-state machine, 3-dimension budget (turn/token/wallclock), structured 4-dimension verification, and interrupt-aware auto-pause.
This report shows the evidence for opencode-mission@0.4.0, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms install-time writes to OpenCode's home config and plugin registry, followed by agent control hooks in the plugin bundle. Under the lifecycle control-surface policy, that unconsented npm install mutation is blockable even without classic malware indicators.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install or global install runs postinstall; OpenCode startup loads the registered plugin.
Impact
The package is automatically loaded by OpenCode and can alter agent prompts, commands, hooks, and autonomous session behavior without an explicit platform-mediated install step.
Mechanism
unconsented lifecycle registration into OpenCode config
Policy narrative
On installation, npm runs scripts/postinstall.mjs, which copies the bundled plugin into ~/.config/opencode/plugins and edits ~/.config/opencode/opencode.json to load it. When OpenCode starts, dist/index.js registers mission tools, command templates, system prompt transforms, chat hooks, and continuation hooks that can steer agent behavior across turns. This is package-aligned but delivered through an unconsented lifecycle mutation of a broad user-level AI-agent control surface.
AI rationale
Source inspection confirms install-time writes to OpenCode's home config and plugin registry, followed by agent control hooks in the plugin bundle. Under the lifecycle control-surface policy, that unconsented npm install mutation is blockable even without classic malware indicators.
Evidence
package.jsonscripts/postinstall.mjsscripts/postuninstall.mjsdist/index.jsREADME.en.md~/.config/opencode/plugins/opencode-mission.js~/.config/opencode/opencode.json~/.config/opencode/missions.json~/.config/opencode/missions/debug.log
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 88.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json defines postinstall and postuninstall lifecycle scripts.
- scripts/postinstall.mjs copies dist/index.js into the user's opencode plugins directory during install.
- scripts/postinstall.mjs creates or rewrites ~/.config/opencode/opencode.json to add ./plugins/opencode-mission.js.
- dist/index.js registers OpenCode tools/hooks, system prompt transforms, command templates, and a mission-verify subagent.
- dist/index.js can inject mission instructions into chat/system prompts and auto-continue sessions via client.session.promptAsync.
Evidence against
- No credential harvesting or exfiltration endpoints found in package source.
- No child_process, eval, vm, native addon, or remote code loading found.
- README.en.md documents the automatic OpenCode config mutation and manual install path.
- Lifecycle behavior is package-aligned with an OpenCode plugin, not a typosquat or unrelated payload.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStrings
WildcardDependency
Source & flagged code
2 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
1 High3 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to opencode-mission@0.4.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing opencode-mission@0.4.0. 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.