domma-js@0.44.6
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest activates an install-time hook that can add package-owned Claude assistance files to the consumer project after a prompt. This is a guarded agent extension setup, with no concrete malicious behavior established by the inspected source.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
npm installation runs the postinstall hook in a node_modules context, then the user accepts the prompt or presses Enter.
Impact
This can add package-authored guidance and configuration used by Claude Code; the inspected evidence does not establish broader control hijacking or data theft.
Mechanism
The hook copies package-supplied agent files to project-root destinations when those destinations do not already exist.
AI rationale
The manifest activates an install-time hook that can add package-owned Claude assistance files to the consumer project after a prompt. This is a guarded agent extension setup, with no concrete malicious behavior established by the inspected source.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js during installation.
- The postinstall script asks whether to copy AI assistance files, with “Y” as the default and only an explicit “n” or “no” skipping.
- The lifecycle code copies package-supplied CLAUDE.md into the consumer project root when absent.
- The CLI has a separate setup command that copies the same package-owned assistance files after a prompt.
- The flagged view template defines ordinary view lifecycle hooks and contains no agent-control behavior in the inspected excerpt.
Evidence against
- The install-time behavior is limited to the package’s own Claude assistance files and skips existing destinations.
- The script’s prompt allows the user to decline; no network or credential transfer is shown in the inspected lifecycle code.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
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.44.6.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.44.6 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.