domma-js@0.52.1
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe install lifecycle can write package-owned AI assistance files into the consumer project after a default-yes prompt. This merits a warning for agent extension lifecycle risk, but the inspected source does not establish a broader control-surface hijack or data transfer.
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 in a non-development, non-CI node_modules context and accepting the prompt or pressing Enter.
Impact
The installation can change the project context available to Claude Code. The inspected settings show project metadata and framework preferences.
Mechanism
The hook copies the package’s CLAUDE.md and .claude directory into the project root when those destinations are absent.
AI rationale
The install lifecycle can write package-owned AI assistance files into the consumer project after a default-yes prompt. This merits a warning for agent extension lifecycle risk, but the inspected source does not establish a broader control-surface hijack or data transfer.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jstemplates/kickstart/.claude/settings.jsonCLAUDE.md.claude/
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 during installation.
- The postinstall hook offers to copy AI assistance files and proceeds unless the user answers “n” or “no”.
- The hook copies the package’s CLAUDE.md and .claude directory into the project root when those destinations do not exist.
- The bundled .claude settings contain project metadata and Domma preferences.
- The CLI also provides a prompted setup-ai command that copies these package-owned files.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
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.1.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.52.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.