domma-js@0.39.2
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source confirms install-time mutation of the consumer project's Claude Code files, with a prompt whose blank response accepts the default. Because the setup copies first-party package files and skips existing destinations, this is an agent extension lifecycle risk rather than a confirmed malicious attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package with npm in a non-CI project under node_modules, then leaving the copy prompt blank or accepting it.
Impact
Package-provided content may influence Claude Code behavior in the consumer project; existing destination paths are skipped.
Mechanism
The hook copies CLAUDE.md and, if absent, the package's .claude directory and other assistance files into the project root.
AI rationale
The source confirms install-time mutation of the consumer project's Claude Code files, with a prompt whose blank response accepts the default. Because the setup copies first-party package files and skips existing destinations, this is an agent extension lifecycle risk rather than a confirmed malicious attack.
Evidence
package.jsonbin/postinstall.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The npm postinstall hook runs bin/postinstall.js during installation.
- The hook prompts whether to copy AI assistance files, but treats a blank answer as acceptance because only “n” or “no” cancels.
- After acceptance, the hook copies package-provided Claude files into the consumer project, including a .claude directory when none exists.
- The CLI also exposes an explicit setup-ai command that prompts before copying those files.
Evidence against
- The postinstall exits in CI and unless the working directory is under node_modules; it also skips when no project root or template is found.
- The copy operation skips destinations that already exist, and the CLI setup requires an explicit command.
- The flagged view template is a generated view scaffold with example hooks, not evidence of the flagged attack behavior.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpublic/dist/domma.esm.jsView file
9patternName = generic_password
severity = medium
line = 9
Medium
bin/postinstall.js
Findings
1 Critical3 High6 Medium4 Low
CriticalAi Agent Control Hijackbin/postinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitedtemplates/view-template/view.js
HighKnown Malware Source Similaritybin/domma-cli.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Patternpublic/dist/domma.esm.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSecret Patternpublic/dist/domma.min.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to domma-js@0.39.2.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.39.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.