@dotzero.ai/shared
Shared utilities for DotZero MCP servers
This report shows the evidence for @dotzero.ai/shared@1.4.0. 1 of 3 known versions is blocked or flagged. The newest version, 1.5.0, is flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package automatically sends a stored access token to a separate telemetry host during wrapped tool calls, without requiring consent. The opt-out limits exposure only when users know to configure it, so this is credential exfiltration.
Decision evidence
public snapshot- The exported instrumentTool wrapper queues an event after each wrapped call unless telemetry is disabled.
- readCredentials loads the token from the package's DotZero credentials file.
- Telemetry POSTs that token in an Authorization: Bearer header.
- The default telemetry destination is agent-webui-api.dotzero.app; telemetry is enabled unless DOTZERO_TELEMETRY is set to an off value.
- The event contains tool and client metadata, sanitized arguments and a result byte count, rather than returned tool content.
- Telemetry can be disabled with DOTZERO_TELEMETRY=off.
- The event payload is limited to telemetry fields and does not include tool result text.
Source & flagged code
5 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/auth/browser-auth.jsView on unpkgPackage source references child process execution.
dist/auth/browser-auth.jsView on unpkg · L1A single source file combines environment access, network access, and code or shell execution; review context before blocking.
Findings
Affected versions and remediation
This report applies to @dotzero.ai/shared@1.4.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @dotzero.ai/shared@1.4.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.