Loading npm security reports…

@tera-system/pro@0.1.4: AI-agent control-surface risk | LPM Firewall

registry / @tera-system/pro / 0.1.4

@tera-system/pro@0.1.4

Tera System Pro ط£آ¢أ¢â€ڑآ¬أ¢â‚¬â€Œ commercial edition with enforced license gate, server sync, and heartbeat verification

AI Security Review

scanned 22d ago · by lpm-firewall-ai

LPM flags this version as an AI-agent control-surface risk. npm postinstall runs an installer against the consumer workspace and plants OpenCode agents, commands, and config under .opencode. It then downloads a vendor-signed bundle and writes it into those same OpenCode paths.

Static reason

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

Trigger

Automatic npm postinstall when the package is installed.

Impact

OpenCode in the consumer project can load planted agents, commands, and MCP config without a separate user setup command.

Mechanism

Unconsented install-time write of OpenCode agents, commands, and config, plus remote bundle apply

Policy narrative

On npm install, postinstall runs scripts/install.js against the consumer workspace, usually INIT_CWD. It copies bundled agents and commands into .opencode and, if no OpenCode config exists, writes .opencode/opencode.json. It then downloads a signed bundle from teranoo.com and writes files into .opencode/agents, .opencode/commands, tera-system, and tools without the ownership checks used in the first copy pass. OpenCode can load that planted control surface on the next run.

AI rationale

The postinstall hook mutates the consumer OpenCode control surface and then applies a remote signed bundle onto the same paths. That is unconsented install-time hijack of a foreign AI-agent config, not an in-package extension load.

Evidence

package.jsonscripts/install.jsscripts/lib/bundle.mjs.opencode/agents.opencode/commands.opencode/opencode.json.opencode/tera-core.manifest.json

Source & flagged code

5 flagged

package.jsonView file

Lines 4-43json

4 "description": "Tera System Pro ط£آ¢أ¢â€ڑآ¬أ¢â‚¬â€Œ commercial edition with enforced license gate, server sync, and heartbeat verification",

5 "license": "SEE LICENSE IN LICENSE.md",

6 "type": "module",

7 "engines": {

8 "node": ">=18"

9 },

10 "files": [

11 "agents",

12 "commands",

13 "core",

14 "tools",

15 "scripts",

16 "MANIFEST.json",

17 "opencode.tera.example.json",

18 "WELCOME.md",

19 "README.md",

20 "LICENSE.md",

21 "RELEASES.md"

22 ],

23 "scripts": {

24 "postinstall": "node scripts/install.js",

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L24

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg · L24

25 "tera-license": "node scripts/tera-license.mjs",

26 "tera-preflight": "node scripts/preflight.mjs",

27 "tera-sync": "node scripts/tera-sync.mjs",

28 "tera-heartbeat": "node scripts/tera-heartbeat.mjs",

29 "tera-bundle": "node scripts/build-bundle.mjs"

30 },

31 "keywords": [

32 "opencode",

33 "plugin",

34 "tera",

35 "governance",

36 "agents",

37 "commercial",

38 "license"

39 ],

40 "publishConfig": {

41 "access": "public"

42 }

43}

scripts/install.jsView file

Lines 1-30javascript

1#!/usr/bin/env node

2/**

3 * @tera/core installer

4 * --------------------------------------------------------------

5 * NON-DESTRUCTIVE + OWNERSHIP-AWARE installer for the Tera System

6 * OpenCode Plugin component.

7 *

8 * Rules:

9 * - Never deletes anything.

10 * - Never overwrites a file it does not own.

11 * - Tracks ownership via `.opencode/tera-core.manifest.json`.

tools/tera-fetch.ps1View file

•path = tools/tera-fetch.ps1 kind = build_helper sizeBytes = 6816 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

tools/tera-fetch.ps1View on unpkg

scripts/build.mjsView file

•matchType = token_shingles matchedPackage = @tera-system/core@0.2.18 matchedPath = scripts/build.mjs matchedIdentity = npm:QHRlcmEtc3lzdGVtL2NvcmU:0.2.18 similarity = 1.000 shingleOverlap = 48 summary = source token shingles overlapped finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

scripts/build.mjsView on unpkg