domma-js@0.53.2
Dynamic Object Manipulation & Modeling API - A complete front-end toolkit.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource inspection found a postinstall setup path that can add first-party Claude Code project files, with blank input treated as approval. The inspected files show ordinary project guidance and preferences, so this warrants a warning rather than a block.
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 as a dependency outside CI, then leaving the copy prompt blank or accepting it.
Impact
The copied guidance may shape future Claude Code work in that project; the inspected settings contain framework preferences, with no confirmed harmful behavior.
Mechanism
The postinstall script copies the package’s Claude guidance and .claude directory into the project root when those destinations are absent.
AI rationale
Source inspection found a postinstall setup path that can add first-party Claude Code project files, with blank input treated as approval. The inspected files show ordinary project guidance and preferences, so this warrants a warning rather than a block.
Evidence
package.jsonbin/postinstall.jstemplates/kickstart/.claude/settings.jsonCLAUDE.md.claude/
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs bin/postinstall.js during installation.
- The hook runs for dependency installs outside CI and asks whether to copy AI assistance files; only an explicit “n” or “no” skips the copy.
- The hook creates the project’s .claude directory only when that destination does not already exist.
- The CLI also offers a user-invoked setup command that copies the same first-party files only to missing destinations.
- The inspected Claude settings contain framework and code-style preferences.
Evidence against
- The inspected setup copies package-provided project guidance and preferences; these settings do not enable telemetry, hooks, or a remote extension channel.
- The install hook skips CI and does not overwrite an existing .claude directory.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscation
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.53.2.
See all versions of domma-js for other recorded verdicts.
- Review the evidence and your use of domma-js@0.53.2 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.