domma-js@0.44.1
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe package has an install-time hook that can add first-party Claude configuration and instructions to the consumer project. Its interactive consent prompt and no-overwrite checks make this a guarded agent extension lifecycle risk rather than a confirmed attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package, followed by accepting the postinstall prompt; alternatively, invoking the setup-ai CLI command and accepting its prompt.
Impact
This can add package-provided instructions and settings that affect later AI-agent behavior; source evidence shows a first-party template setup flow, not a confirmed control hijack.
Mechanism
The hook copies the package's CLAUDE.md, .claude directory, blueprints, and types into the project root when those destinations do not exist.
AI rationale
The package has an install-time hook that can add first-party Claude configuration and instructions to the consumer project. Its interactive consent prompt and no-overwrite checks make this a guarded agent extension lifecycle risk rather than a confirmed attack.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js automatically after installation.
- The postinstall script prompts before copying AI assistance files into the consumer project.
- The postinstall copy writes only when destination files or directories do not already exist.
- The separately invoked setup-ai command also copies first-party AI files and skips existing destinations.
Evidence against
- The postinstall checks that it is running from node_modules and skips CI environments.
- The template view source contains ordinary view lifecycle examples and no active network or credential behavior.
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.44.1.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.44.1 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.