@rfdtech/components@2.4.0
Shared React component library for Clet projects
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource confirms that npm installation automatically invokes setup, which modifies configuration for multiple AI coding tools and the user's Codex configuration. This meets the policy threshold for blocking install-time mutation of a broad AI-agent control surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package with npm, which runs its postinstall hook.
Impact
AI tools may load this package's MCP server after restart, without the consumer separately invoking setup.
Mechanism
The hook launches the setup CLI in the consumer project directory. The CLI detects supported AI tools and writes MCP server entries to their configuration files.
Policy narrative
The npm postinstall hook runs setup automatically. Setup detects installed AI tools and adds this package's MCP server to their configuration, including user-level Codex configuration. This is unconsented install-time mutation of several AI-tool control surfaces.
AI rationale
Source confirms that npm installation automatically invokes setup, which modifies configuration for multiple AI coding tools and the user's Codex configuration. This meets the policy threshold for blocking install-time mutation of a broad AI-agent control surface.
Evidence
package.jsonscripts/postinstall.mjsdist/mcp/installers/setup.jsdist/mcp/installers/claude.jsdist/mcp/installers/cursor.jsdist/mcp/installers/codex.jsdist/mcp/installers/opencode.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 97.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs a postinstall script during installation.
- The postinstall script automatically runs the setup CLI in the consumer project directory.
- Setup writes MCP configuration for detected Claude Code, Cursor, Codex, and OpenCode installations; Codex configuration is written under the user's home directory.
- The installers add this package's MCP server to AI-tool configuration without a separate setup command.
Evidence against
- The setup targets this package's own MCP server and skill files.
- Project-scoped tools are detected before their installers run, and the installer merges a named server entry into existing configuration.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystem
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
6 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 unpkgdist/next.cjsView file
1Object.defineProperty(exports,Symbol.toStringTag,{value:`Module`});const e=require("./next-BsR5ktCe.cjs");exports.AppBody=e.vn,exports.AppHeader=e.Nr,exports.AppHeaderActions=e.Pr,...
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/next.cjsView on unpkg · L1Findings
2 Critical2 High4 Medium4 Low
CriticalTrojan Source Unicodedist/next-BsR5ktCe.cjs
CriticalTrigger Reachable Dangerous Capabilitydist/index.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limiteddist/index.css
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/next.cjs
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @rfdtech/components@2.4.0.
See all versions of @rfdtech/components for other recorded verdicts.
- Avoid installing @rfdtech/components@2.4.0. 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.