registry / AI-agent control-surface risk / @tera-system/core
@tera-system/core
Tera System OpenCode Plugin — governance core, 25 agents, 38 commands, distribution tools (personal edition)
This report shows the evidence for @tera-system/core@0.6.2. 11 of 22 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 20d ago · by lpm-firewall-aiInspected source establishes automatic mutation of OpenCode's shared control surface, including enabled third-party commands, rather than setup confined to a package-owned extension. This meets the blocking policy despite ownership and backup safeguards.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm postinstall runs scripts/install.js.
Impact
Installation changes available agent instructions and capabilities; subsequent OpenCode use can launch the configured third-party commands.
Mechanism
The installer resolves the consumer workspace, copies agent and command files into shared OpenCode directories, and creates an enabled MCP configuration when absent.
Policy narrative
Installing the package automatically runs its installer against the consumer workspace. It populates OpenCode's shared agent and command directories and creates a configuration enabling third-party MCP commands. Preserving existing conflicting files limits overwrites but does not prevent unconsented creation of this broader agent control surface.
AI rationale
Inspected source establishes automatic mutation of OpenCode's shared control surface, including enabled third-party commands, rather than setup confined to a package-owned extension. This meets the blocking policy despite ownership and backup safeguards.
Evidence
package.jsonscripts/install.jsopencode.tera.example.json.opencode/agents.opencode/commands.opencode/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 automatically runs scripts/install.js after installation.
- The installer defaults to the consumer workspace and installs agents and commands into OpenCode's shared control directories.
- The installer creates .opencode/opencode.json when absent, without an explicit setup gate.
- The installed configuration enables third-party MCP commands through npx.
Evidence against
- Existing conflicting files are preserved, and updates to tracked files receive backups.
- The inspected build helper performs packaging and hashing; no credential exfiltration was established.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/install.jsView file
10* - Never overwrites a file it does not own.
L11: * - Tracks ownership via `.opencode/tera-core.manifest.json`.
L12: * - Only updates files it owns, always keeping a backup first.
L13: * - Idempotent: re-running is safe; identical files are skipped.
L14: * - Never touches an existing user `opencode.json`.
L15: *
...
L65: function copyFile(src, dest) {
L66: fs.mkdirSync(path.dirname(dest), { recursive: true });
L67: fs.copyFileSync(src, dest);
L68: }
...
L70: function loadOwnership(target) {
L71: const p = path.join(target, ".opencode", MANIFEST_NAME);
Findings
1 Critical4 High5 Medium6 Low
CriticalAi Agent Control Hijackscripts/install.js
HighInstall Time Lifecycle Scriptspackage.json
HighShips High Entropy Blobassets/project-control/TeraPricingCalculator.xlsx
HighKnown Malware Source Similarityscripts/build.mjs
HighKnown Malware Source Fingerprint Signaturescripts/build.mjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helpertools/tera-fetch.ps1
MediumShips Compressed Blobassets/project-control/TeraPricingCalculator.xlsx
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @tera-system/core@0.6.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @tera-system/core@0.6.2. 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.
Versions
22 known versions0.6.2latestshownMaliciousSoft block: AI-agent control surfaceBlockPublishedOct 3, 2026, 7:22 AM0.6.0MaliciousSoft block: AI-agent control surfaceBlockPublishedSep 26, 2026, 8:07 PM0.5.0SuspiciousAgent extension lifecycle riskWarnPublishedSep 24, 2026, 7:27 AM0.4.1MaliciousSoft block: AI-agent control surfaceBlockPublished