momentic@3.52.5
 [![npm]](https://www.npmjs.com/package/momentic)
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection contradicts the scanner's install-time and credential-exfiltration claims: there is no lifecycle hook, and the flagged self-install and skill writes are explicit CLI command paths. No concrete malicious behavior was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Explicit momentic CLI commands such as upgrade or install-skills.
Impact
No unconsented install-time execution, credential theft, foreign package overwrite, or persistence was confirmed.
Mechanism
User-invoked test automation, project setup, updates, and telemetry.
AI rationale
Source inspection contradicts the scanner's install-time and credential-exfiltration claims: there is no lifecycle hook, and the flagged self-install and skill writes are explicit CLI command paths. No concrete malicious behavior was found.
Evidence
package.jsonbin/cli.jsREADME.mdskills/momentic-test.md
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
Evidence against
- package.json has no preinstall, install, postinstall, or prepare lifecycle script.
- The only package entrypoint is the momentic CLI, so code runs after an explicit user command.
- The self-update install is reached only by the explicit upgrade command.
- Skill installation is an explicit deprecated command with a required editor choice and writes only the selected project skill directory.
- Observed telemetry and API hosts are Momentic or standard error-reporting endpoints; no credential harvesting or unconsented exfiltration was confirmed.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
17 flaggedpackage.jsonView file
•name = momentic; similarTo = moment
Medium
Typosquat Name
Package name is suspiciously similar to a popular package name.
package.jsonView on unpkgbin/cli.jsView file
11import K4 from 'truncate-json';
L12: import Ul, { supportsColorStderr, supportsColor, Chalk } from 'chalk';
L13: import vNe from 'safe-stable-stringify';
...
L30: import m0, { randomUUID, createHash, createHmac, timingSafeEqual } from 'crypto';
L31: import * as pat from 'child_process';
L32: import { execFile, execSync, exec, execFileSync, spawn as spawn$1 } from 'child_process';
...
L37: import { registerInstrumentations } from '@opentelemetry/instrumentation';
L38: import { UndiciInstrumentation } from '@opentelemetry/instrumentation-undici';
L39: import { resourceFromAttributes } from '@opentelemetry/resources';
...
L170: Original error: ${n}
L171: `}async function F3({dryRun:e,operation:t}){try{return await t()}catch(n){throw new Error(lMe({err:n,dryRun:e}),{cause:n})}}function Xr
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
bin/cli.jsView on unpkg · L11Findings
4 Critical11 High4 Medium6 Low
CriticalCredential Exfiltrationbin/cli.js
CriticalBrowser Credential Phishingbin/cli.js
CriticalTrigger Reachable Dangerous Capabilitybin/cli.js
CriticalPrevious Version Dangerous Deltabin/cli.js
HighChild Processbin/cli.js
HighShellstatic/assets/index-DI2KFrsZ.js
HighSame File Env Network Executionbin/cli.js
HighCredential Redirect Persistencebin/cli.js
HighEntrypoint Foreign Package Code Overwritebin/cli.js
HighCommand Output Exfiltrationbin/cli.js
HighRemote Agent Bridgebin/cli.js
HighTrigger Reachable Credential Exfiltration
Affected versions and remediation
This report applies to momentic@3.52.5.
See all versions of momentic for other recorded verdicts.
- Review the evidence and your use of momentic@3.52.5 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.