domma-js@0.53.0
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found an install-time prompt for copying project-local assistance files, with existing destinations preserved. The AI settings are project preferences, and the bundle network helper has no package-selected recipient; no concrete attack behavior was established.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
The postinstall hook runs in eligible node_modules contexts and asks whether to copy assistance files.
Impact
The observed effect is project scaffolding; no credential disclosure, agent content export, or other attack behavior was found.
Mechanism
The hook copies missing project-local files and skips existing destinations; the supplied settings contain project metadata and coding preferences.
AI rationale
Source inspection found an install-time prompt for copying project-local assistance files, with existing destinations preserved. The AI settings are project preferences, and the bundle network helper has no package-selected recipient; no concrete attack behavior was established.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest’s postinstall script runs bin/postinstall.js.
- The postinstall hook checks its install context, presents a copy prompt with a decline option, and copies project-local files only when their destinations are absent.
- The copied Claude settings contain project paths and Domma coding preferences; they do not enable hooks, permissions, or content export.
- The separate setup-ai CLI command also prompts before copying assistance files.
- Both bundles expose a general HTTP helper that calls fetch with the supplied URL and request options; no package-selected recipient was found.
- The view template logs lifecycle events; its example API request is commented out.
Evidence against
- The postinstall prompt defaults to proceeding unless the user answers no, and the hook can add project-local assistance files.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
8 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 Critical4 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
HighKnown Malware Source Fingerprint Signaturebin/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
Affected versions and remediation
This report applies to domma-js@0.53.0.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.53.0 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.