registry / @threenative/core / 0.3.5

@threenative/core@0.3.5

The small vanilla Three.js game runtime foundation.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The source confirms automatic, guarded setup of package-owned agent tools during installation. This leaves a first-party agent extension lifecycle risk, but no concrete malicious action was established.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source

Trigger

The npm postinstall hook, unless setup is opted out or the project does not qualify.

Impact

Configured agents may launch the package's tools for that project.

Mechanism

The hook merges package-owned MCP server entries into project-scoped agent configuration files.

AI rationale

Evidence

package.jsonscripts/postinstall.mjsscripts/ensure-mcp.mjsmcp/install.mjsmcp/servers.mjs.mcp.json.codex/config.toml.cursor/mcp.json.vscode/mcp.json.gemini/settings.jsonopencode.json.zed/settings.json

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.

Evidence for warning

package.json runs scripts/postinstall.mjs, which calls runMcpSetup automatically.
The setup can be skipped with THREENATIVE_SKIP_MCP_SETUP=1 or true.
Installation targets projects that declare @threenative/core and registers project-scoped agent configuration files.
The installer writes merged server configuration when it changes a config.
The registered commands point to MCP tools shipped with this package.
The Blender runtime receiver is a local file reader used to load a selected recipe.

Evidence against

The installer skips node_modules and this package's own project, and avoids projects that do not declare it.
The inspected Blender and UI runtime operations did not establish a separate malicious action.

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsTelemetry

Source & flagged code

10 flagged

package.jsonView file

•scripts.postinstall = node ./scripts/postinstall.mjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node ./scripts/postinstall.mjs

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

mcp/launch.mjsView file

•matchType = normalized_sha256 matchedPackage = @threenative/core@0.3.4 matchedPath = mcp/launch.mjs matchedIdentity = npm:QHRocmVlbmF0aXZlL2NvcmU:0.3.4 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.

mcp/launch.mjsView on unpkg

7* here: `threenative-engine-mcp` publishes an `exports` map with only an `import` condition, which L8: * `createRequire().resolve` refuses, and the answer we want is the directory rather than a L9: * specifier's entry point. Walking `node_modules` upward from both the project and this package

Medium

Dynamic Require

Package source references dynamic require/import behavior.

mcp/launch.mjsView on unpkg · L7

scripts/apply-three-patch.mjsView file

18options.consumerRoot ?? L19: process.env.INIT_CWD ?? L20: process.env.npm[redacted] ?? L21: process.cwd(), L22: ); L23: const threeRoot = options.threeRoot ?? resolveThreeRoot(consumerRoot, packageRoot); L24: const manifestPath = path.join(threeRoot, "package.json"); L25: const manifest = await readJson(manifestPath, "Three.js package manifest"); ... L53: const resolver = createRequire(path.join(root, "package.json")); L54: const entry = resolver.resolve("three"); L55: const resolvedRoot = findPackageRoot(entry); ... L110: try {

Low

Weak Crypto

Package source references weak cryptographic algorithms.

scripts/apply-three-patch.mjsView on unpkg · L18

mcp/install.mjsView file

1Install-time code directly mutates a foreign AI-agent control surface: L1: import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs"; L2: import path from "node:path"; L3: import { CODEX_MCP_SERVERS, mergeMcpServers } from "./servers.mjs"; L4: ... L45: label: "Claude Code", L46: file: ".mcp.json", L47: format: "mcpServers", L48: }), L49: Object.freeze({ id: "codex", label: "Codex", file: ".codex/config.toml", format: "codex" }), L50: Object.freeze({ id: "cursor", label: "Cursor", file: ".cursor/mcp.json", format: "mcpServers" }), L51: Object.freeze({ id: "vscode", label: "VS Code", file: ".vscode/mcp.json", format: "vscode" }), ... L55: file: ".gemini/settings.json", Write operation from mcp/install.mjs: L1: import { existsSync, mkdirSync, readFileSync, writeFileSync }

Critical

Ai Agent Control Hijack

Source creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.

mcp/install.mjsView on unpkg · L1

gpl/convert.pyView file

•path = gpl/convert.py kind = build_helper sizeBytes = 6997 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

gpl/convert.pyView on unpkg

gpl/fixtures/make_world_fixture.pyView file

•path = gpl/fixtures/make_world_fixture.py kind = payload_in_excluded_dir sizeBytes = 7323 magicHex = [redacted]

High

Payload In Excluded Dir

Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.

gpl/fixtures/make_world_fixture.pyView on unpkg

mcp/blender-server.mjs#virtual:normalized:round1View file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 3

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

mcp/blender-server.mjs#virtual:normalized:round1View on unpkg

mcp/blender-server.mjsView file

•matchType = previous_version_dangerous_delta matchedPackage = @threenative/core@0.3.3 matchedIdentity = npm:QHRocmVlbmF0aXZlL2NvcmU:0.3.3 similarity = 0.593 summary = stored previous version shares package body but lacks this dangerous source file

High

Previous Version Dangerous Delta

This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.

mcp/blender-server.mjsView on unpkg

Source & flagged code

10 flagged · loading source

package.jsonView file

•scripts.postinstall = node ./scripts/postinstall.mjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•scripts.postinstall = node ./scripts/postinstall.mjs

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

mcp/launch.mjsView file

High

Known Malware Source Similarity

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

mcp/launch.mjsView on unpkg

Findings

1 Critical5 High6 Medium7 Low

CriticalAi Agent Control Hijackmcp/install.mjs

HighInstall Time Lifecycle Scriptspackage.json

HighPayload In Excluded Dirgpl/fixtures/make_world_fixture.py

HighSemantic Analysis Limitedmcp/blender-server.mjs#virtual:normalized:round1

HighKnown Malware Source Similaritymcp/launch.mjs

HighPrevious Version Dangerous Deltamcp/blender-server.mjs

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumDynamic Requiremcp/launch.mjs

MediumNetwork

MediumEnvironment Vars

MediumShips Build Helpergpl/convert.py

MediumStructural Risk Force Deep Review

Affected versions and remediation

This report applies to @threenative/core@0.3.5.

See all versions of @threenative/core for other recorded verdicts.

Review the evidence and your use of @threenative/core@0.3.5 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: 2026-10-20 01:15:29.444Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Runtime surface

Behavioral surface

Source & flagged code