run402@4.134.0
CLI for Run402 — full-stack backend infrastructure for AI agents: Postgres, auth, storage, serverless functions and atomic deploys. Paid with x402/MPP. Includes $0.03 image generation.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s Buzz doctor command sends limited runtime and diagnostic telemetry without an apparent disclosure in the reviewed documentation. It is opt-out and user-triggered, so this merits a warning rather than a block; the reviewed flows show no credential theft or other attack behavior.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A user runs the doctor command with --buzz; telemetry is enabled unless RUN402_TELEMETRY=0.
Impact
The service receives coarse diagnostic and runtime-version information. The reviewed payload does not include credentials, hostnames, paths, or file contents.
Mechanism
The command queues a bounded diagnostic event and launches a worker that posts it to the configured Run402 API origin.
AI rationale
The package’s Buzz doctor command sends limited runtime and diagnostic telemetry without an apparent disclosure in the reviewed documentation. It is opt-out and user-triggered, so this merits a warning rather than a block; the reviewed flows show no credential theft or other attack behavior.
Evidence
lib/diagnostic-telemetry.mjslib/doctor.mjsconfigDir()/diagnostic-events-v1.json
Network endpoints1
configured API origin: /client-diagnostic-events/v1
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The Buzz diagnostic telemetry event is limited to a random event ID, timestamp, event/check codes, coarse OS family, Node and Run402 versions, fixture ID, and install context.
- Buzz doctor queues telemetry by default; it is disabled only when RUN402_TELEMETRY=0.
- The queued events are POSTed to /client-diagnostic-events/v1 at the configured API origin.
- Telemetry is triggered by running the explicit doctor --buzz flow, not by installation or package import.
Evidence against
- No install lifecycle scripts are declared.
- The flagged cloud metadata address occurs in a test fixture for public-address validation.
- The SDK blob requests send the project service key to the configured Run402 API as part of requested blob operations.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggedgit-remote-run402.mjsView file
34import net from "node:net";
L35: import { spawn } from "node:child_process";
L36: import { daemonSocketPath, daemonRunnerPath, DAEMON_PROTOCOL_VERSION, cliVersion, forwardableEnv } from "./lib/daemon-path.mjs";
High
Child Process
Package source references child process execution.
git-remote-run402.mjsView on unpkg · L34•matchType = normalized_sha256
matchedPackage = run402@4.71.0
matchedPath = git-remote-run402.mjs
matchedIdentity = npm:cnVuNDAy:4.71.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
git-remote-run402.mjsView on unpkgsdk/dist/node/deploy-manifest.jsView file
844try {
L845: tsx = (await import("tsx/esm/api"));
L846: }
Findings
1 Critical7 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltalib/ci.mjs
HighChild Processgit-remote-run402.mjs
HighCloud Metadata Accesslib/buzz-doctor.test.mjs
HighRuntime Package Installlib/dev.mjs
HighSemantic Analysis Limitedlib/doctor-source-scan.test.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritylib/diagnostic-telemetry.mjs
HighKnown Malware Source Similaritygit-remote-run402.mjs
HighKnown Malware Source Similaritylib/update-check.test.mjs
MediumDynamic Requiresdk/dist/node/deploy-manifest.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to run402@4.134.0.
See all versions of run402 for other recorded verdicts.
- Review the evidence and your use of run402@4.134.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.