registry / AI-agent control-surface risk / @xzy-ai/pi-c2
@xzy-ai/pi-c2
PI extension: delegate work to isolated in-process subagents through model-callable tools
This report shows the evidence for @xzy-ai/pi-c2@0.0.4. 1 of 2 known versions is blocked or flagged. The newest version, 0.84.2-1.821.2026, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source confirms an automatic postinstall overwrite of a foreign Pi coding-agent host, expanding its extension API. This is a concrete unconsented AI-agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall during installation
Impact
Alters a separate AI-agent host's extension control surface without user action.
Mechanism
foreign Pi host discovery and bundled patch overwrite
Policy narrative
On npm installation, the package locates the global Pi host and copies/overwrites its files with a bundled patch. This is an unconsented install-time modification of a foreign AI-agent host and adds an extension command-context capability. Although the code includes backup and rollback logic and no credential exfiltration was found, the lifecycle mutation itself meets the blocking boundary.
AI rationale
The source confirms an automatic postinstall overwrite of a foreign Pi coding-agent host, expanding its extension API. This is a concrete unconsented AI-agent control-surface mutation.
Evidence
package.jsonscripts/postinstall.mjsscripts/pi-coding-agent@0.84.2.patch@earendil-works/pi-coding-agent/dist/core/extensions/loader.js@earendil-works/pi-coding-agent/dist/core/extensions/runner.js@earendil-works/pi-coding-agent/dist/core/session-manager.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 96.0% confidence with low false-positive risk.
Evidence for policy risk
- npm postinstall executes scripts/postinstall.mjs.
- Postinstall locates the globally installed @earendil-works/pi-coding-agent host.
- It applies a bundled patch and writes changed files into that foreign host package.
- Patch exposes command-context creation to extensions, expanding the host agent control surface.
Evidence against
- No install-time network request or credential collection was found.
- The script creates a backup and attempts rollback on failure.
- The bundled patch is static and scoped to the named Pi host.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Oversized source lightweight scan
Source & flagged code
7 flagged · loading sourcepackage.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 unpkgindex.jsView file
26321*/
L26322: fork(...middleware) {
L26323: const composer = new _Composer(...middleware);
High
2570function hasPreloadFlags() {
L2571: const execArgv = process.execArgv;
L2572: for (let i = 0; i < execArgv.length; i++) {
Findings
6 High4 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processindex.js
HighShellindex.js
HighCredential Redirect Persistenceindex.js
HighEntrypoint Foreign Package Code Overwriteindex.js
HighCommand Output Exfiltrationindex.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @xzy-ai/pi-c2@0.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @xzy-ai/pi-c2@0.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.