domma-js@0.45.0
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe install hook performs guarded setup of package-owned AI assistance files in the consumer project. This warrants a warning for agent extension lifecycle risk, but the inspected code does not establish a concrete malicious attack or unconsented mutation.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
npm installation invokes the postinstall hook; copying proceeds unless the user answers no.
Impact
If accepted, package-provided Claude assistance files become part of the project and may affect later Claude Code use; no active attack was established from the inspected source.
Mechanism
The script copies missing AI assistance files from package templates into the project root. The CLI provides a separate setup-ai command with its own confirmation prompt.
AI rationale
The install hook performs guarded setup of package-owned AI assistance files in the consumer project. This warrants a warning for agent extension lifecycle risk, but the inspected code does not establish a concrete malicious attack or unconsented mutation.
Evidence
package.jsonbin/postinstall.jsbin/domma-cli.jsCLAUDE.md.claude/
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package postinstall hook runs bin/postinstall.js during installation.
- The install script asks whether to copy AI assistance files and returns when the user answers no.
- On acceptance, the install script can copy CLAUDE.md and a .claude directory into the project root.
- The CLI exposes setup-ai as an explicit command and prompts before copying the same package-owned files.
Evidence against
- The inspected code shows a consent prompt and skips the copy when the user declines.
- The inspected copy logic preserves existing destination files and no credential collection or network transmission was found in these paths.
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.45.0.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.45.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.