3a-factory@4.1.2
Enterprise Feature-local Spec Package workflow for Claude, Gemini, and Cursor (3A-Factory)
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not malicious install-hook abuse because automatic lifecycle execution exits before the project mutation. The explicit CLI still modifies AI-agent control surfaces, so it warrants a warning for dangerous capability rather than a block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user explicitly invokes the 3a-factory CLI outside an npm automatic lifecycle.
Impact
The tool can change how supported AI coding agents behave in the target project; no covert execution or data transfer was confirmed.
Mechanism
Writes packaged agent instructions and command adapters into the target project.
AI rationale
This is not malicious install-hook abuse because automatic lifecycle execution exits before the project mutation. The explicit CLI still modifies AI-agent control surfaces, so it warrants a warning for dangerous capability rather than a block.
Evidence
package.jsondist/install.jsAGENTS.md.agents/templates.agents/contracts.agents/schemas.agents/rules.agents/skills.agents/agents.agents/configs.claude/commands.claude/skills.gemini/commands.cursor/rules
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package runs its installer from postinstall, but the installer detects npm automatic lifecycle events and exits before scaffolding.
- An explicit CLI invocation writes workflow files and command or rule files into a consumer project's AI-agent configuration locations.
- The installer can create new files and, with --force, overwrite differing files after making a backup.
Evidence against
- No network, credential collection, shell execution, remote payload loading, or self-dependency is present in the inspected source.
- Automatic npm lifecycle execution is guarded to skip the project-writing behavior.
Behavioral surface
DynamicRequireEnvironmentVarsFilesystem
HighEntropyStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node -e "const f=require('fs'),{execSync}=require('child_process');if(!f.existsSync('dist/install.js')&&f.existsSync('scripts/build.js'))execSync('node scripts/build.js',{stdio:'in...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.preinstall = node -e "const f=require('fs'),{execSync}=require('child_process');if(!f.existsSync('dist/install.js')&&f.existsSync('scripts/build.js'))execSync('node scripts/build.js',{stdio:'in...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node dist/install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg27"preinstall": "node -e \"const f=require('fs'),{execSync}=require('child_process');if(!f.existsSync('dist/install.js')&&f.existsSync('scripts/build.js'))execSync('node scripts/build.js',{stdio:'inherit'})\"",
"prepublishOnly": "npm run build",
"postinstall": "node dist/install.js"
Findings
2 Critical1 High5 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalAi Agent Control Hijackdist/install.js
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/install.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSuspicious Lifecycle Evidencepackage.json
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to 3a-factory@4.1.2.
See all versions of 3a-factory for other recorded verdicts.
- Review the evidence and your use of 3a-factory@4.1.2 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.