registry / AI-agent control-surface risk / thorta
thorta
OpenCode preconfigured with the THORTA development environment, agents, and skills
This report shows the evidence for thorta@1.0.4, the only known version.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThis matches the blockable policy for unconsented lifecycle mutation of foreign or broad AI-agent control surfaces, even though the content appears package-aligned and no exfiltration endpoint was found. The behavior is install-triggered, persistent in user config locations, and affects agent instruction/control files outside the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install or postinstall runs node bin/cli.js --sync
Impact
User/home agent behavior can be altered without explicit consent, including installed skills and persistent instruction files for OpenCode/Claude-style agents.
Mechanism
lifecycle-triggered AI-agent config and instruction file writes
Policy narrative
Installing thorta runs bin/cli.js --sync through both install and postinstall. That code modifies user and project OpenCode-related configuration, copies package-controlled skills and agents into ~/.config/opencode and ~/.opencode, and plants AGENTS.md/CLAUDE.md instructions without a user-invoked setup step.
AI rationale
This matches the blockable policy for unconsented lifecycle mutation of foreign or broad AI-agent control surfaces, even though the content appears package-aligned and no exfiltration endpoint was found. The behavior is install-triggered, persistent in user config locations, and affects agent instruction/control files outside the package.
Evidence
package.jsonbin/cli.jsagent/Build T.mdagent/Plan T.mdskills/graphify/SKILL.md~/.config/opencode/skills/*/SKILL.md~/.opencode/skills/*/SKILL.md~/.config/opencode/agent/Build T.md~/.config/opencode/agents/Build T.md~/.opencode/agent/Plan T.md~/.opencode/agents/Plan T.md~/.config/opencode/AGENTS.md~/.config/opencode/CLAUDE.md~/.opencode/AGENTS.md~/.opencode/CLAUDE.md~/opencode.json./opencode.json
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 96.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs node bin/cli.js --sync on both install and postinstall.
- bin/cli.js main() always rewrites cwd opencode.json and may rename ~/opencode.json during lifecycle.
- bin/cli.js syncSkillsAndRules writes package SKILL.md files into ~/.config/opencode and ~/.opencode.
- bin/cli.js writes AGENTS.md and CLAUDE.md into ~/.config/opencode and ~/.opencode with package-supplied agent instructions.
- Generated OpenCode config grants bash/write/edit tools and disables default build/plan agents when CLI launches.
Evidence against
- No external network endpoints or credential exfiltration found in inspected files.
- Agent/build scripts appear user-invoked after CLI run, not lifecycle-triggered by --sync.
- Writes target OpenCode-related locations rather than arbitrary shell startup or OS persistence files.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/cli.js --sync
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.install = node bin/cli.js --sync
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg•scripts.postinstall = node bin/cli.js --sync
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/cli.jsView file
1Install-time AI-agent control hijack evidence:
L30: if (!fs.existsSync(dir)) {
L31: fs.mkdirSync(dir, { recursive: true });
L32: }
...
L38: path.join(userHome, ".config", "opencode"),
L39: path.join(userHome, ".opencode")
L40: ];
L41:
L42: // Limpa o diretório .opencode local no packageRoot se existir para não poluir o explorador
L43: const localOpencode = path.join(packageRoot, ".opencode");
L44: if (fs.existsSync(localOpencode)) {
...
L63: const skillContent = fs.readFileSync(srcSkillPath, "utf8");
L64: fs.writeFileSync(destSkillPath, skillContent, "utf8");
Payload evidence from skills/ui-ux-pro-max/SKILL.md:
L1: ---
L2: name: ui-ux-pro-max
Findings
1 Critical3 High6 Medium4 Low
CriticalAi Agent Control Hijackbin/cli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/cli.js
HighSame File Env Network Executiondev-server.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to thorta@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing thorta@1.0.4. 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.