Telemetry in npm packages.
These packages send usage, machine or identifying details, such as the hostname, email, local paths or command arguments, to their publisher or an analytics service by default. LPM Firewall warns about them, and users can choose to block them with lpm config firewall. These packages are not malware. Packages that send credentials, file contents, prompts or code, or that send data to an unrelated collector, are blocked and listed under Data exfiltration instead.
Packages — page 11
651 packages with an LPM warning, newest scan first. Showing 481–528.
The payload wires runtime event and error telemetry into the server, enabled by default with an environment-variable opt-out. Its attributes are filtered, but the package README does not...
The package sends an environment-derived terminal identifier with user-invoked web search requests. The disclosure is limited to the Codex request path, so this is a telemetry warning rat...
The runtime records telemetry by default during server operation, but its package documentation does not disclose that behavior. The source filters sensitive attributes and provides disab...
The widget automatically sends visitor measurement events when consent is absent or refused, as long as Do Not Track and Global Privacy Control are not set. This conflicts with the docume...
The CLI sends undisclosed runtime telemetry by default to the vendor’s analytics endpoint, including usage outcomes and persistent or account-linked identifiers. The source filters common...
Classify as suspicious runtime telemetry: on widget load failure, the SDK sends page and JWT-derived context to Zerohash's collector without a documented opt-out. The behavior serves the...
The SDK automatically sends undisclosed failure diagnostics to the vendor collector, including the page origin, browser user-agent, and selected JWT claims. Because this occurs only durin...
This is a legitimate widget SDK whose hosted script loads on an explicit render call. However, load failures automatically send decoded JWT claims and browser/page metadata to the vendor’...
The package's purpose and default collector are consistent with a ZeroHash React widget, but its failure-triggered telemetry sends browser and page-origin data without disclosure or an op...
The package’s MCP server silently starts presence reporting by default when a token is configured, sending browser tab counts to ShowMyTab. This is undisclosed runtime telemetry, so warn...
The default postinstall hook reports limited package and runtime metadata to the package’s own service. Install-time telemetry is warning-level under the review rules, while the other fla...
The source shows default-enabled runtime telemetry sent to WalletConnect Pulse, with no package-level disclosure or opt-out established in the reviewed material, so this warrants a warnin...
The package sends runtime usage telemetry to PostHog by default, and the inspected README does not disclose it. The captured fields appear limited to operational metadata, and users can o...
The bundle includes default-on runtime telemetry that reports the embedding app domain and client metadata, without an evident disclosure or opt-out in the package manifest. The inspected...
The package automatically reports device fingerprint and interaction telemetry during authentication, and the inspected source does not disclose or expose a way to disable it. The destina...
The package sends runtime telemetry without disclosure in its README, so this merits a warning. The observed fields are limited configuration metadata and the telemetry service provides a...
The package’s postinstall hook automatically runs IBM Telemetry, and its configuration specifies an IBM metrics endpoint. The README discloses telemetry and an opt-out, but default instal...
The package has no install hook or evident credential theft, and the flagged backfill is an explicit admin tool. Its runtime analytics nevertheless sends identifiable usage events to Post...
This is undisclosed runtime telemetry enabled by default through scaffolding. It sends board and slice metadata beyond the cost tracking described by the consent prompt, so warn rather th...
The package’s install hook sets up its own launchers and binaries, consistent with its stated purpose. However, TUI startup triggers an undisclosed, daily background request for the lates...
This is undisclosed runtime telemetry: local quota snapshots are forwarded to the Mikka service during normal daemon operation. The inspected code sends provider tokens only to their prov...
The package discloses runtime telemetry and provides opt-outs, but configures Sentry to collect broad PII, including AI inputs and outputs through supported integrations. That creates a m...
The package sends default-on runtime usage telemetry from CLI invocations without disclosing it in the package README. The inspected events contain usage and platform metadata, not prompt...
The plugin explicitly requests feature-exposure telemetry during runtime, without disclosure or an opt-out visible in the reviewed package. No credential theft or unrelated data collectio...
The package automatically sends its version to the vendor’s policy endpoint for selected commands, and the documented update-check opt-out does not suppress that request. The narrow data...
The source sends runtime command telemetry by default, including a signed-in Cleo user ID or persistent anonymous ID, while the README does not disclose that collection. An opt-out is ava...
The browser client performs an undisclosed public IP lookup automatically during initialization, with a related geolocation request used for closest-peer selection. The behavior has a pla...
The package performs default runtime telemetry after successful payments, sending a merchant wallet, settlement transaction identifier, and resource URL to its Intel service. The opt-out...
The source shows default runtime error-tracking initialization without a disclosure or opt-out found in the package documentation, so this warrants a telemetry warning. The flagged wallet...
The package automatically sends free-form search terms to host-configured analytics after successful searches, without an explicit opt-in or documented disable control. This is a runtime...
The analytics helper includes the machine hostname in telemetry and defaults to enabled without an explicit consent step. Since the package entry point does not invoke it automatically, t...
The CLI sends runtime usage telemetry to PostHog without disclosure or an opt-out documented in the package README, which warrants a warning. The visible custom fields are coarse command...
The command runner automatically passes raw command arguments to analytics, while the available code only shows the token being redacted. Because the analytics implementation and destinat...
This is suspicious under the install-time telemetry rule: the postinstall hook records and flushes telemetry by default without explicit consent. The reviewed event is limited to install/...
The deploy credential finding is not supported: the key is used for the LangSmith backend, and the saved value is the deployment name. However, CLI commands send runtime telemetry by defa...
The TUI sends runtime telemetry by default, including a persistent device ID and user or account identifiers alongside launch metadata. The inspected payload contains no prompts, file con...
The bundle automatically sends incomplete form contents on page exit, without an explicit submission. The destination is the widget’s configured service and the package is a contact form,...
This is not credential exfiltration: the engagement token authenticates to the configured Halfcycle telemetry service, and the record contains run metadata rather than raw tool input. The...
The automatic postinstall downloader attaches a hash derived from the current project name to outgoing request headers. Install-time telemetry is enabled by default, so this warrants a wa...
The package has a plausible team capture purpose, but this version also repairs Codex hooks automatically to enable per-prompt discovery. Because prompts are sent to the backend without s...
The package’s runtime onboarding flow sends event telemetry linked by a stable anonymous ID without an apparent opt-out or CLI disclosure, so this merits a warning. The inspected payload...
The package’s purpose supports sending story interaction analytics to its own service, and the reviewed payload does not show sensitive credentials or machine details. Analytics is enable...
The package’s MetaMask client dependency enables runtime analytics by default, and the wrapper does not configure an opt-out. The observed events carry usage metadata such as app identity...
The flagged credential and command findings were not supported: the status-line uses PAPI-specific credentials with the configured endpoint, and its settings write requires an explicit in...
The CLI silently sends limited first-run telemetry on each machine, with no disclosure or opt-out found in the package. The payload does not include credentials or user content, so this w...
The postinstall behavior fits the package’s stated artifact-delivery purpose, and I found no evidence of credential theft or unrelated actions. However, an authenticated install sends a p...
The package sends disclosed, limited runtime analytics automatically, but I found no way to disable them. This warrants a warning for default telemetry; the source does not show credentia...
The package’s behavior fits its documented Canary CLI purpose, and its telemetry is disclosed. Because runtime telemetry includes repository and agent metadata without a documented way to...