domma-js@0.51.0
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package defines an install-time hook that offers to write package-owned Claude Code files into the consumer project, creating a concrete agent configuration capability. The prompt and destination checks make this a guarded first-party setup, so the appropriate result is a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Package installation in a node_modules directory outside CI, followed by accepting the prompt or providing an answer other than no.
Impact
May add project instructions and Claude Code settings that affect later agent use; the inspected code does not establish malicious control or data theft.
Mechanism
Copies CLAUDE.md, .claude, blueprints, and types from the package template into project paths when those destinations do not already exist.
AI rationale
The package defines an install-time hook that offers to write package-owned Claude Code files into the consumer project, creating a concrete agent configuration capability. The prompt and destination checks make this a guarded first-party setup, so the appropriate result is a warning rather than a block.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.js
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js during installation.
- The install hook runs in a node_modules context outside CI and prompts before copying AI assistance files; answering no skips the copy.
- The hook copies package-provided Claude Code files into the consumer project only when the destination paths do not already exist.
- The CLI exposes the same setup as an explicit setup-ai command, asks before copying, and does not overwrite existing destinations.
Evidence against
- Inspected code shows no credential collection, network transmission, or remote payload execution in the flagged install and setup paths.
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.0.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.51.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.