domma-js@0.51.8
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe postinstall hook performs project-root writes to Claude Code control files and treats the default empty response as consent. This meets the policy for blocking unconsented postinstall mutation of a foreign AI-agent control surface.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
npm runs the package postinstall hook in a node_modules install context outside CI or the package's development tree.
Impact
Package-provided instructions or settings can be added to the consuming project's AI-agent control surface without an affirmative opt-in.
Mechanism
The hook prompts for permission, then copies files into the project root for any response other than “n” or “no”; an empty response proceeds with copying.
Policy narrative
The package declares an automatic postinstall hook. In an eligible install context, the hook asks whether to copy AI assistance files but proceeds on an empty or otherwise non-negative answer, then writes CLAUDE.md and .claude/ into the project root when they are absent. This is unconsented install-time mutation of an AI-agent control surface.
AI rationale
The postinstall hook performs project-root writes to Claude Code control files and treats the default empty response as consent. This meets the policy for blocking unconsented postinstall mutation of a foreign AI-agent control surface.
Evidence
package.jsonbin/postinstall.jsCLAUDE.md.claude/
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 98.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs bin/postinstall.js automatically after installation.
- The install hook asks whether to copy AI assistance files, but treats every answer except “n” or “no”—including an empty response—as approval.
- The hook copies CLAUDE.md and creates a .claude directory in the consuming project when those destinations do not exist.
- The CLI also exposes a separately prompted setup-ai command that copies these files.
- templates/view-template/view.js contains ordinary view lifecycle examples; it does not explain or mitigate the install-time writes.
Evidence against
- The install hook skips development and CI contexts and checks that it is running from node_modules.
- The file-copy operations preserve existing destination files and directories.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscation
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.51.8.
See all versions of domma-js for other recorded verdicts.
- Avoid installing domma-js@0.51.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.