domma-js@0.51.10
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install-time hook can modify Claude-related project configuration, and its yes-by-default prompt leaves a real consent concern. The behavior is limited to package-owned setup files, so it warrants a warning rather than a publish block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package in a node_modules context outside CI, followed by an empty or affirmative response to the prompt.
Impact
This may add Claude-specific project guidance and settings. The source supports a guarded, package-owned setup capability, but no separate attack behavior was established.
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 install-time hook can modify Claude-related project configuration, and its yes-by-default prompt leaves a real consent concern. The behavior is limited to package-owned setup files, so it warrants a warning rather than a publish block.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jstemplates/view-template/view.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
- package.json runs bin/postinstall.js during installation.
- The hook runs in a node_modules install context, asks whether to copy AI assistance files, and stops when the user answers no. Its prompt defaults to yes, so an empty response proceeds.
- The hook copies the package's .claude directory into the project only if that destination does not already exist.
- The CLI exposes setup-ai as a separate command and also prompts before copying files.
- The flagged view template contains ordinary view lifecycle examples, not an attack behavior.
Evidence against
- The reviewed source shows no confirmed data theft, remote payload execution, or destructive behavior.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
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.10.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.51.10 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.