domma-js@0.48.0
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe automatic postinstall path can add package-owned assistant configuration, but it prompts first and skips existing destinations. This supports a warning for guarded agent setup rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Installing the package in a project where the postinstall conditions pass, followed by accepting its prompt.
Impact
Accepted setup can introduce package-supplied assistant guidance and configuration into the project; the inspected source does not establish credential theft, remote execution, or an unconsented write.
Mechanism
The hook prompts to copy assistance files and copies missing CLAUDE.md, .claude, blueprints, and types paths from the package templates. The CLI provides a separate interactive setup route.
AI rationale
The automatic postinstall path can add package-owned assistant configuration, but it prompts first and skips existing destinations. This supports a warning for guarded agent setup rather than a malicious verdict.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jsCLAUDE.md.claude/blueprints/types/
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js automatically after installation.
- The postinstall hook prompts before copying AI assistance files into the project.
- The hook creates CLAUDE.md only when that file does not already exist.
- The CLI offers a separate interactive setup path that also creates only missing assistance files.
- The view template is a generated view scaffold with a template URL and lifecycle methods; it contains no attack behavior.
Evidence against
- The postinstall hook can add package-provided Claude assistance files to a consumer project after an affirmative prompt; this is a guarded agent configuration capability, not a confirmed attack.
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.48.0.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.48.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.