registry / @tera-system/pro / 0.2.13

@tera-system/pro@0.2.13

Tera System Pro — commercial edition (thin): system files are fetched from teranoo.com as a signed bundle; enforced license gate + heartbeat

AI Security Review

scanned 2h ago · by lpm-firewall-ai

LPM flags this version as an AI-agent control-surface risk. On npm postinstall, the package alters the consumer workspace's OpenCode control surface and enables MCP launch commands. It also retrieves a signed remote bundle and writes its contents into workspace directories.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Installing the package with npm lifecycle scripts enabled.

Impact

A package installation can establish enabled agent tools and introduce remotely supplied workspace content without an explicit setup command.

Mechanism

Automatic OpenCode configuration creation and remote bundle deployment.

Policy narrative

npm invokes the installer automatically. When the target project has no OpenCode configuration, it writes one that enables MCP commands, including npx-installed tools. In the same lifecycle run it downloads a vendor-signed thin bundle and applies its files to workspace directories. Although it preserves conflicting configuration and validates bundle signatures, this is unconsented postinstall mutation of a broad AI-agent control surface.

Rationale

The automatic lifecycle changes the consumer's OpenCode configuration and activates command-capable MCP integrations without an explicit user setup action. This meets the install-time AI-agent control-surface abuse blocking policy.

Evidence

package.jsonscripts/install.jsopencode.tera.example.jsonscripts/lib/bundle.mjs.opencode/opencode.json.opencode/opencode.tera.example.json.opencode/agents/.opencode/commands/

@tera-system/pro@0.2.13

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code