@momentic/qa-node
A Node.js build of qa for Windows Server 2016, which Bun does not support.
This report shows the evidence for @momentic/qa-node@0.30.1. 0 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s core API-key traffic is directed through the Momentic API client, but the executable also sends runtime error reports to a fixed Sentry endpoint with PII collection enabled. This is undisclosed runtime telemetry, so it warrants a warning rather than a malicious verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI catches a command failure and captures the exception.
Impact
Error reports may disclose user or request information to the package publisher’s Sentry project.
Mechanism
Sentry is configured with a fixed ingest endpoint and sendDefaultPii enabled, which permits user details and request metadata in reports.
AI rationale
The package’s core API-key traffic is directed through the Momentic API client, but the executable also sends runtime error reports to a fixed Sentry endpoint with PII collection enabled. This is undisclosed runtime telemetry, so it warrants a warning rather than a malicious verdict.
Evidence
mo.mjs
Network endpoints1
o4506426201800704.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 79.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package is a Momentic QA CLI with `mo.mjs` as its executable entrypoint.
- The CLI reports caught command failures through its Sentry error-capture path.
- The Sentry configuration sends reports to a fixed Sentry host with `sendDefaultPii:true`; the bundled Sentry settings enable user details, cookies, HTTP headers and bodies, and query parameters when that flag is true.
- The Momentic API client sends its API key in an Authorization header, and its server selection uses the Momentic default or a server supplied through configuration.
Evidence against
- The manifest has no lifecycle scripts, so this reporting is not triggered during installation.
- The package’s main function is a QA CLI, and the API key transport is associated with its Momentic API client.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
12 flaggedmo.mjsView file
35import { EventEmitter } from 'events';
L36: import { execSync, spawnSync, spawn as spawn$1 } from 'child_process';
L37: import { randomUUID, createHash, generateKeyPairSync, privateDecrypt, constants } from 'node:crypto';
...
L41: import X6e, { mkdtemp, writeFile, rm, mkdir, open, readFile as readFile$1, stat, readdir as readdir$1, link, chmod, constants as constants$1, rename } from 'node:fs/promises';
L42: import { validateHeaderValue } from 'http';
L43: import { finished, pipeline } from 'node:stream/promises';
...
L47: const require$1 = createRequire(import.meta.url);
L48: var $Ye=Object.create;var yv=Object.defineProperty;var eXe=Object.getOwnPropertyDescriptor;var tXe=Object.getOwnPropertyNames;var nXe=Object.getPrototypeOf,rXe=Object.prototype.has...
L49: `).join(`
Critical
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution with blocking evidence.
mo.mjsView on unpkg · L3513import { EventEmitter as EventEmitter$1, errorMonitor } from 'node:events';
L14: import * as E4 from 'node:http';
L15: import { createServer, request } from 'node:http';
...
L18: import { AsyncLocalStorage, AsyncResource } from 'node:async_hooks';
L19: import r4e, { execFile, spawn } from 'node:child_process';
L20: import Wn, { readFile, readdir, openAsBlob, rmSync, writeFileSync, renameSync, realpathSync, openSync, fchmodSync, closeSync, createReadStream, existsSync, readFileSync as readFile...
...
L28: import { Readable } from 'node:stream';
L29: import { gunzipSync, createGzip } from 'node:zlib';
L30: import * as ll from 'node:net';
...
L36: import { execSync, spawnSync, spawn as spawn$1 } from 'child_process';
L37: import { randomUUID, createHash, generateKeyPairSync, privateDecry
Findings
4 Critical6 High5 Medium4 Low
CriticalSame File Env Network Executionmo.mjs
CriticalDownload Executemo.mjs
CriticalRemote Asset Decode Executemo.mjs
CriticalTrigger Reachable Dangerous Capabilitymo.mjs
HighChild Processmo.mjs
HighShellmo.mjs
HighCredential Redirect Persistencemo.mjs
HighCommand Output Exfiltrationmo.mjs
HighTrigger Reachable Command Output Exfiltrationmo.mjs
HighSemantic Analysis Limitedmo.mjs
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filemo.mjs
Affected versions and remediation
This report applies to @momentic/qa-node@0.30.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @momentic/qa-node@0.30.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.