registry / @tera-system/pro / 0.2.28
@tera-system/pro@0.2.28
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 26d ago · by lpm-firewall-aiThe package has an automatic remote payload and OpenCode control-surface setup during installation. Signature verification and conflict handling reduce, but do not remove, the risk from opaque package-controlled extension content.
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
A package-controlled signed release can alter first-party OpenCode agent configuration and workspace files during installation.
Mechanism
The installer fetches a remote bundle, verifies it with its packaged key, and writes accepted bundle files to target directories; it may also create an OpenCode MCP configuration.
AI rationale
The package has an automatic remote payload and OpenCode control-surface setup during installation. Signature verification and conflict handling reduce, but do not remove, the risk from opaque package-controlled extension content.
Evidence
scripts/install.jsscripts/lib/bundle.mjsopencode.tera.example.json.opencode/agents/.opencode/commands/tera-system/tools/.opencode/opencode.json
Network endpoints1
teranoo.com/api/tera-system/bundle
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package runs its installer automatically through a postinstall hook.
- The installer fetches a bundle from teranoo.com during installation.
- The fetched bundle is applied as files in the consumer workspace, including OpenCode agent and command locations.
- When no OpenCode configuration exists, installation creates one that enables local MCP commands, including npx-installed tools.
Evidence against
- The bundle verifier checks an embedded public-key signature before accepting a bundle.
- The installer preserves an existing differing OpenCode configuration rather than overwriting it.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 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.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: *
...
L75: function copyFile(src, dest) {
L76: fs.mkdirSync(path.dirname(dest), { recursive: true });
L77: fs.copyFileSync(src, dest);
L78: }
...
L80: function loadOwnership(target) {
L81: const p = path.join(target, ".opencode", MANIFEST_NAME);
Findings
1 Critical3 High4 Medium5 Low
CriticalAi Agent Control Hijackscripts/install.js
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Similarityscripts/build.mjs
HighKnown Malware Source Fingerprint Signaturescripts/build.mjs
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tera-system/pro@0.2.28.
See all versions of @tera-system/pro for other recorded verdicts.
- Review the evidence and your use of @tera-system/pro@0.2.28 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.