registry / @apilift/cli / 1.4.38
@apilift/cli@1.4.38
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe flagged behaviors resolve to Apilift CLI flows, local capture, schema validation, and pseudonymous measurement delivery. No install hook or concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI linking or another CLI command activates the relevant runtime paths; session audit requires a supplied session or transcript.
Impact
No unrelated credential transfer, remote response execution, or agent configuration mutation was established.
Mechanism
Linking sends a code to the configured Apilift site. The collector derives metrics from local transcripts; the capture server uses authenticated loopback access, and the evaluated helpers are package-embedded.
AI rationale
The flagged behaviors resolve to Apilift CLI flows, local capture, schema validation, and pseudonymous measurement delivery. No install hook or concrete attack behavior was found.
Network endpoints1
apilift.dev
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists build and test scripts, with no install lifecycle hook.
- The session-audit finding location is within bundled tokenizer data; the audit requires a supplied session or transcript and reads that transcript locally.
- The collector examines Codex or Claude transcripts to derive measurements, then sends pseudonymized session and usage metrics with an installation token to Apilift after a CLI command.
- The native host processes native-messaging input from standard input.
- CLI linking uses the configured Apilift site, defaulting to https://apilift.dev, and saves the returned installation token.
- The dynamic-code findings are generated schema validation and an embedded process-inspection helper; the capture server binds to loopback and requires a bearer token.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 flaggeddist/apilift.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @apilift/cli@1.4.37
matchedIdentity = npm:QGFwaWxpZnQvY2xp:1.4.37
similarity = 0.667
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/apilift.jsView on unpkg76const {workerData}=require('node:worker_threads');
L77: const {spawn}=require('node:child_process');
L78: const state=new Int32Array(workerData.memory,0,4), value=new Float64Array(workerData.memory,16,1);
High
23778sourceCode = this.opts.code.process(sourceCode, sch);
L23779: const makeValidate = new Function(`${names_1.default.self}`, `${names_1.default.scope}`, sourceCode);
L23780: const validate2 = makeValidate(this, this.scope.get());
High
Findings
2 Critical4 High3 Medium6 Low
CriticalRemote Response Code Executiondist/apilift-capture-server.js
CriticalPrevious Version Dangerous Deltadist/apilift.js
HighChild Processdist/apilift.js
HighEvaldist/apilift.js
HighCredential Redirect Persistencedist/apilift.js
HighCross File Remote Execution Contextdist/apilift.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @apilift/cli@1.4.38.
See all versions of @apilift/cli for other recorded verdicts.
- Review the evidence and your use of @apilift/cli@1.4.38 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.