registry  /  apteva  /  0.24.14

apteva@0.24.14

AI agent platform with multi-thread orchestration, MCP integrations, and dashboard

AI Security Review

scanned 12d ago · by lpm-firewall-ai

No confirmed malicious attack surface was found. The package is a thin npm launcher that installs and runs package-aligned native binaries from the project's GitHub releases.

Static reason
One or more suspicious static signals were detected.
Trigger
npm install postinstall or user running the apteva bin
Impact
Installs/runs Apteva binaries as requested by the package; no source-confirmed exfiltration or persistence beyond package-aligned ~/.apteva install layout.
Mechanism
GitHub release binary installer and CLI shim
Rationale
The suspicious primitives are explained by a package-aligned binary installer and CLI shim; direct source inspection found no credential harvesting, covert exfiltration, obfuscation, or unconsented agent control-surface mutation. The lack of release integrity verification is a supply-chain hardening gap, but not evidence that this package version is malicious.
Evidence
package.jsoninstall.jscli.jsREADME.md~/.apteva/versions/${VERSION}/~/.apteva/bin/current~/.apteva/bin/apteva~/.apteva/bin/apteva-server~/.apteva/bin/apteva-core./apteva./apteva-server./apteva-core
Network endpoints2
github.com/apteva/apteva/releases/download/v${VERSION}/apteva-${VERSION}-${platform}-${arch}.tar.gzgithub.com/apteva/apteva/releases/tag/v${VERSION}

Decision evidence

public snapshot
AI called this Clean at 82.0% confidence as Benign with medium false-positive risk.
Evidence for block
  • package.json defines postinstall: node install.js
  • install.js downloads a platform tarball from github.com/apteva/apteva releases and extracts it with tar
  • install.js writes binaries/symlinks under APTEVA_HOME or ~/.apteva and copies fallback binaries into the package dir
  • cli.js spawns the resolved apteva binary with inherited stdio/env
Evidence against
  • Network use is limited to package-aligned GitHub release download URL derived from apteva/apteva and package version
  • No credential, token, npmrc, ssh, or broad file harvesting found by source search
  • No exfiltration endpoint or covert network destination found
  • No eval/vm/Function, obfuscated strings, prompt/reviewer manipulation, or AI-agent control-surface writes found
  • README describes this as a binary launcher for the Apteva CLI/server/core, matching install.js and cli.js behavior
Behavioral surface
Source
ChildProcessEnvironmentVarsFilesystemNetworkShell
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 2 file(s), 10.1 KB of source, external domains: github.com

Source & flagged code

4 flagged · loading source
package.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg
install.jsView file
29const http = require("http"); L30: const { execSync } = require("child_process"); L31:
High
Child Process

Package source references child process execution.

install.jsView on unpkg · L29
27const path = require("path"); L28: const https = require("https"); L29: const http = require("http"); L30: const { execSync } = require("child_process"); L31: ... L40: // by hand; both files are short and the shape is fixed. L41: const APTEVA_HOME = process.env.APTEVA_HOME || path.join(os.homedir(), ".apteva"); L42: const VERSIONS_DIR = path.join(APTEVA_HOME, "versions");
High
Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution; review context before blocking.

install.jsView on unpkg · L27

Findings

4 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall.js
HighShell
HighSame File Env Network Executioninstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings