@bfrs/agentic-components@0.8.8
Shiprocket agentic component library and documentation showcase.
AI Security Review
scanned 2d ago · by lpm-firewall-aiSource confirms that package installation automatically mutates consumer AGENTS.md or CLAUDE.md files and rewrites package scripts. This is an unconsented lifecycle change to agent control files, supporting a block despite the package context being product-focused and no network transfer being shown.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package when setup is not skipped and its context file exists.
Impact
Installation changes files that guide coding agents and alters project build commands without a separate setup command.
Mechanism
The hook copies package context into the consumer project, appends a reference to AGENTS.md or CLAUDE.md, and adds a lint guard to package scripts.
Policy narrative
The package declares an automatic postinstall hook. In consumer lifecycle context, unless setup is skipped, the hook copies its context file into the project, edits agent instruction files, and changes package scripts. This is an unrequested install-time mutation of the consumer's agent control surface and build configuration.
AI rationale
Source confirms that package installation automatically mutates consumer AGENTS.md or CLAUDE.md files and rewrites package scripts. This is an unconsented lifecycle change to agent control files, supporting a block despite the package context being product-focused and no network transfer being shown.
Evidence
package.jsonscripts/postinstall.cjsBFRS_AGENTIC_COMPONENTS.mdAGENTS.mdCLAUDE.md
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 93.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs scripts/postinstall.cjs automatically during installation.
- The hook targets consumer-project AGENTS.md and CLAUDE.md files and appends a reference to package-provided agent context.
- The hook copies that context into the consumer project and writes a lint command into its package.json scripts.
- The hook also prepends its lint command to selected consumer build scripts.
Evidence against
- The appended agent reference points to package context about using the component library; the inspected source shows no credential collection or network transfer.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg55"postinstall": "node scripts/postinstall.cjs",
"dev": "vite --host 0.0.0.0",
"build": "npm run build:lib && npm
High
Suspicious Lifecycle Evidence
package.json runs scripts/postinstall.cjs automatically during installation.
package.jsonView on unpkg · L55•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/postinstall.cjsView file
Findings
1 Critical4 High3 Medium4 Low
CriticalAi Agent Control Hijackscripts/postinstall.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/fonts.css
HighKnown Malware Source Fingerprint Signaturescripts/lint/cli.cjs
HighSuspicious Lifecycle Evidencepackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @bfrs/agentic-components@0.8.8.
See all versions of @bfrs/agentic-components for other recorded verdicts.
- Avoid installing @bfrs/agentic-components@0.8.8. 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.