domma-js@0.52.3
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe source shows a reachable install hook that may create project-level Claude files with a default-accept prompt. The copied files appear package-owned and convention-focused, so this supports a warning for guarded agent setup rather than a malicious verdict.
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
Installing the package as a dependency outside the development and CI contexts, with a project root found.
Impact
This can introduce project-level Claude context and settings during dependency installation; no confirmed malicious behavior was identified.
Mechanism
The hook prompts and can copy the package's .claude directory, CLAUDE.md, blueprints, and types into the project when destination paths are absent.
AI rationale
The source shows a reachable install hook that may create project-level Claude files with a default-accept prompt. The copied files appear package-owned and convention-focused, so this supports a warning for guarded agent setup rather than a malicious verdict.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jstemplates/kickstart/.claude/settings.json
Decision evidence
public snapshotAI called this Suspicious at 86.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js during installation.
- The hook can run from a normal node_modules install outside CI when it finds the project root.
- The hook asks whether to copy AI assistance files, but only an explicit “n” or “no” declines; other answers continue.
- The hook copies the package’s .claude directory and other assistance files into the project when those destinations are absent.
- The separate setup-ai CLI command is user-invoked, and its inspected target copies a missing CLAUDE.md from the package template.
- The inspected Claude settings describe Domma project paths and preferences.
Evidence against
- The hook skips development and CI contexts and requires a node_modules installation context.
- The inspected settings excerpt shows project preferences; no content-export behavior was identified.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
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.52.3.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.52.3 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.