base_parts_ai@1.0.64
jaskle base_parts_ai
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no npm install lifecycle hook, but its explicit CLI flow silently accepts a server-reported update and installs a global package tarball before rerunning. That creates a concrete update-based execution risk warranting a warning; the inspected evidence does not establish a separate attack sufficient to block publication.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the jcx CLI and the configuration service reports a newer version.
Impact
The installed package version can change and execute in the user’s global CLI environment without a distinct upgrade confirmation.
Mechanism
The updater treats confirmation as yes, installs a versioned tarball from the package publisher’s file host using npm with force, then reruns the CLI.
AI rationale
The package has no npm install lifecycle hook, but its explicit CLI flow silently accepts a server-reported update and installs a global package tarball before rerunning. That creates a concrete update-based execution risk warranting a warning; the inspected evidence does not establish a separate attack sufficient to block publication.
Evidence
lib/ai_utils.jsbin/jcx.js
Network endpoints3
jai.jaskle.cnjdwfiles.oss-cn-hangzhou.aliyuncs.comregistry.npmmirror.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Running the jcx command calls fetchConfig before executing its selected configuration module.
- When the server reports a newer version, fetchConfig sets confirmation to yes without asking the user, installs a package tarball globally with force, and reruns the CLI.
- The package has no preinstall, install, or postinstall lifecycle hook; the __postinstall name is not an npm lifecycle hook.
- The inspected jcodex path helper identifies a user Codex .env location; the jcx setup creates a Codex directory and derives an AGENTS.md path.
Evidence against
- The automatic upgrade occurs during an explicit CLI command, rather than during npm installation.
- The inspected excerpts do not establish credential theft or an unrelated account action.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcebin/jcx.jsView file
7var path = require('path');
L8: var { execSync } = require('child_process');
L9: var { Command } = require('commander');
High
•Runtime or CLI code links a write operation to an explicit external AI-agent control path:
#!/usr/bin/env node
'use strict';
var fs = require('fs');
var os = require('os');
var path = require('path');
var { execsync } = require('child_process');
var { command } = require('commander');
function getbuildcfg(cmd) {
var buildcfg = {};
buildcfg.details = cmd.details;
try {
var npmrootg = execsync('npm root -g', { encoding: 'utf8' }).trim();
var codexpkgpath = path.jo
High
External Ai Agent Control Surface Mutation
Runtime or CLI source writes behavior-bearing configuration into a user or project AI-agent control surface.
bin/jcx.jsView on unpkgbin/jgrok.jsView file
Findings
1 Critical6 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltalib/ucx.js
HighChild Processbin/jcx.js
HighShell
HighSandbox Evasion Gated Capabilitylib/ai_utils.js
HighExternal Ai Agent Control Surface Mutationbin/jcx.js
HighRuntime Package Installlib/ai_utils.js
HighSemantic Analysis Limitedlib/ucx.js#virtual:normalized:round1
MediumDynamic Requirebin/jgrok.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to base_parts_ai@1.0.64.
See all versions of base_parts_ai for other recorded verdicts.
- Review the evidence and your use of base_parts_ai@1.0.64 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.