domma-js@0.51.3
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install hook mutates a consumer project’s Claude configuration surface, but only after an interactive prompt and only for missing destinations. Classify this first-party lifecycle setup as a warning, with no confirmed malicious attack behavior.
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 development or CI; the hook then prompts the user.
Impact
It can add Claude Code context and settings to the consumer project; the inspected code does not establish credential exposure or remote control.
Mechanism
After the prompt, the hook copies files such as CLAUDE.md and .claude into the project only when the destinations do not already exist.
AI rationale
The install hook mutates a consumer project’s Claude configuration surface, but only after an interactive prompt and only for missing destinations. Classify this first-party lifecycle setup as a warning, with no confirmed malicious attack behavior.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs bin/postinstall.js during installation.
- The install hook asks whether to copy AI assistance files and stops when the user answers no.
- The hook copies CLAUDE.md only when the project does not already contain it.
- The CLI also exposes setup-ai as an explicit command; its copy logic likewise preserves existing destinations.
Evidence against
- The hook skips development and CI contexts and runs only when the working directory is under node_modules.
- Inspected behavior shows first-party file copying, with no network request or remote payload execution.
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.3.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.51.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.