registry / @depup/expo__cli / 57.0.22-depup.2

@depup/expo__cli@57.0.22-depup.2

The Expo CLI (with updated dependencies)

AI Security Review

scanned 1mo ago · by lpm-firewall-ai

Running any CLI command with telemetry enabled detects the surrounding coding agent and sandbox. It sends their identifiers with command telemetry to Expo's telemetry endpoint.

Static reason

One or more suspicious static signals were detected.

Trigger

A user runs the CLI without EXPO_NO_TELEMETRY or EXPO_OFFLINE.

Impact

Discloses coding-agent identity, agent session ID, and sandbox provider to a remote service.

Mechanism

Coding-agent and sandbox fingerprinting added to telemetry events.

Attack narrative

The altered CLI automatically records telemetry when a command runs. Its added detector dependency identifies a coding agent and obtains its ID and session ID; the telemetry layer also adds sandbox identity. These values are placed into the event context and sent in a POST batch to the configured remote telemetry endpoint. This is unrelated to normal Expo command operation and creates a concrete environment-fingerprinting and data-exfiltration path.

AI rationale

The package contains a complete, automatically invoked path that fingerprints coding-agent and sandbox environments and transmits the resulting identifiers. Although it has no install hook, the collection is concrete and unconsented when the CLI is used.

Evidence

package.jsonbuild/bin/clibuild/src/utils/telemetry/utils/agent.jsbuild/src/utils/telemetry/Telemetry.jsbuild/src/utils/telemetry/clients/FetchClient.jsbuild/src/utils/telemetry/utils/constants.js

Network endpoints1

@depup/expo__cli@57.0.22-depup.2

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code