Loading npm security reports…

@tera-system/pro@0.2.14: Malicious npm security report (Block) | LPM Firewall

registry / @tera-system/pro / 0.2.14

@tera-system/pro@0.2.14

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

The postinstall hook mutates the consumer workspace's OpenCode control surface. It also fetches a signed remote bundle and writes its contents into agent-control and project directories.

Static reason

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

Trigger

npm installation of the package

Impact

A package-controlled signer can deliver files that are automatically written into the consumer's AI-agent configuration and project workspace.

Mechanism

Postinstall remote bundle download and OpenCode configuration injection

Attack narrative

Installing the package runs scripts/install.js without a user command. That installer retrieves a remote signed bundle, applies it to the consumer workspace, and creates OpenCode agent-control files and configuration when absent. Signature verification limits who can supply the bundle but does not obtain consent for the automatic control-surface mutation.

Rationale

The package has an automatic postinstall chain that downloads package-controlled content and mutates a consumer AI-agent control surface. This is concrete install-hook abuse rather than a user-invoked setup flow.

Evidence

package.jsonscripts/install.jsscripts/lib/bundle.mjs.opencode/agents.opencode/commands.opencode/opencode.jsontera-systemtoolsproject-control

Network endpoints1

/api/tera-system/bundle

Source & flagged code

4 flagged

package.jsonView file

Lines 9-48json

9 },

10 "files": [

11 "scripts",

12 "core/project-control",

13 "MANIFEST.json",

14 "opencode.tera.example.json",

15 "WELCOME.md",

16 "README.md",

17 "LICENSE.md",

18 "RELEASES.md"

19 ],

20 "bin": {

21 "tera-restore": "scripts/install.js",

22 "tera-pro-restore": "scripts/install.js",

23 "tera-license": "scripts/tera-license.mjs",

24 "tera-sync": "scripts/tera-sync.mjs",

25 "tera-heartbeat": "scripts/tera-heartbeat.mjs",

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

27 },

28 "scripts": {

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

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L29

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg · L29

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

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

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

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

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

35 },

36 "keywords": [

37 "opencode",

38 "plugin",

39 "tera",

40 "governance",

41 "agents",

42 "commercial",

43 "license"

44 ],

45 "publishConfig": {

46 "access": "public"

47 }

48}

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.manifest.json`.

scripts/build.mjsView file

•matchType = normalized_sha256 matchedPackage = @tera-system/pro@0.2.2 matchedPath = scripts/build.mjs matchedIdentity = npm:QHRlcmEtc3lzdGVtL3Bybw:0.2.2 similarity = 1.000 summary = normalized source hash matched 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