The source confirms a serious TLS validation weakness affecting authenticated BigQuery traffic, so this warrants a warning. It does not establish malicious exfiltration or another concrete block-eligible attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A piece action or trigger sends an HTTP request through the shared client.
Impact
An attacker able to intercept network traffic could potentially access bearer credentials or BigQuery request data.
Mechanism
The client sets Node’s TLS verification environment variable to disable certificate checks before calling fetch.
AI rationale
The source confirms a serious TLS validation weakness affecting authenticated BigQuery traffic, so this warrants a warning. It does not establish malicious exfiltration or another concrete block-eligible attack.
Evidence
src/index.jspackage.json
Network endpoints1
bigquery.googleapis.com/bigquery/v2
Decision evidence
public snapshot
AI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
package.json points to src/index.js and declares no lifecycle hooks.
The bundled HTTP client disables Node TLS certificate verification inside each request.
The entrypoint creates a shared instance of that client and uses it for bearer-authenticated BigQuery requests.
The configured API host is BigQuery’s Google API endpoint; the inspected source shows no unrelated recipient.
Evidence against
The inspected source establishes a TLS validation weakness, but not an attacker-controlled destination or an active interception.
The package manifest declares no install-time script.
48${h}
L49: `+await e.crypto.sha256DigestHex(y),P=await D6(e.crypto,e.securityCredentials.secretAccessKey,s,e.region,o),S=await Tu(e.crypto,P,_),T=`${Qk} Credential=${e.securityCredentials.acc...
L50: To learn more about authentication and Google APIs, visit:
High
Child Process
Package source references child process execution.