registry / Install hook abuse / @firestitch/component-tools
@firestitch/component-tools
@firestitch/component-tools
This report shows the evidence for @firestitch/component-tools@18.0.18, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete install-hook abuse chain affecting the consumer's files and Git remote. The editor settings are benign-looking, but they do not justify destructive deletion, commit, and push during dependency installation.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install runs the postinstall lifecycle hook.
Impact
Consumer editor settings can be destroyed; the consumer repository can receive and publish an unwanted commit.
Mechanism
Install-time deletion and replacement of .vscode plus Git commit and push commands.
Attack narrative
On installation, postinstall.js resolves the consumer project three directories above its working directory. It removes that project's .vscode Git submodule, runs git rm, creates a commit, pushes to the configured remote, then recursively deletes and replaces .vscode. These are unconsented install-time mutations of a foreign project and its repository.
AI rationale
This is a concrete install-hook abuse chain affecting the consumer's files and Git remote. The editor settings are benign-looking, but they do not justify destructive deletion, commit, and push during dependency installation.
Evidence
package.jsonpostinstall.jslibs/env.js.vscode.git
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package automatically runs postinstall.js during npm installation.
- The install hook deinitializes and removes the consumer's .vscode Git submodule, commits the removal, and pushes it to the configured remote.
- The install hook recursively deletes the consumer project's .vscode directory and replaces it with package-provided files.
- The target is calculated three directories above the install working directory, reaching the consumer project.
Evidence against
- The bundled VS Code settings contain editor preferences only.
- No credential harvesting, remote payload download, or hidden binary loading was found.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystem
UrlStrings
NoLicense
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg33"postinstall": "node postinstall.js"
High
Suspicious Lifecycle Evidence
The package automatically runs postinstall.js during npm installation.
package.jsonView on unpkg · L33•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgwebpack.package.jsView file
Findings
4 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencepostinstall.js
HighSuspicious Lifecycle Evidencepostinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirewebpack.package.js
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @firestitch/component-tools@18.0.18.
The versions list below shows the verdict for each recorded version.
- Avoid installing @firestitch/component-tools@18.0.18. 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.