base_parts_ai@1.0.65
jaskle base_parts_ai
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe automatic global install of a remote package release creates unresolved supply-chain risk and warrants a warning. The manifest does not define an npm lifecycle hook, and the inspected agent-configuration locations do not establish lifecycle abuse or a separate attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running a CLI command that calls `fetchConfig` when the remote configuration advertises a newer version.
Impact
The update process may replace the globally installed package and run installation behavior contained in the downloaded release.
Mechanism
The update code hardcodes confirmation to yes, invokes global npm installation of a versioned tarball, and reruns the CLI.
AI rationale
The automatic global install of a remote package release creates unresolved supply-chain risk and warrants a warning. The manifest does not define an npm lifecycle hook, and the inspected agent-configuration locations do not establish lifecycle abuse or a separate attack.
Evidence
lib/ai_utils.jsbin/ucx.js
Network endpoints3
jai.jaskle.cnjdwfiles.oss-cn-hangzhou.aliyuncs.comregistry.npmmirror.com
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json defines command scripts and a `__postinstall` key, but no npm `preinstall`, `install`, or `postinstall` lifecycle hook.
- CLI execution calls `fetchConfig`; when the fetched version is newer, the update path sets confirmation to yes without prompting.
- The update path installs a versioned package tarball globally with npm, then reruns the CLI.
- The Claude helper excerpt concerns a cache path; the Codex helper excerpt concerns account-directory name validation.
- The `jcx setapi` command is user-invoked and describes writing selected configuration to `~/.codex`.
Evidence against
- No source inspected establishes a package lifecycle trigger or an unrelated consumer-control-surface mutation.
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.65.
See all versions of base_parts_ai for other recorded verdicts.
- Review the evidence and your use of base_parts_ai@1.0.65 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.