T09 · Insecure Skill Coding Practices
- Location
scripts/bellwire.mjs:238- Finding
Management bearer tokens can be transmitted to an untrusted API origin
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its Bellwire notification purpose, but review is warranted because bearer tokens can be sent to an unvalidated API URL when the endpoint is overridden.
Install only if you trust Bellwire and can keep the API endpoint configuration under your control. Before using it, lock BELLWIRE_API_URL to the official Bellwire origin or a trusted HTTPS self-hosted origin, keep all Bellwire tokens in a real secret manager, and require explicit confirmation for delete, revoke, mode-change, and token-creation operations.
scripts/bellwire.mjs:238Management bearer tokens can be transmitted to an untrusted API origin
assets/examples/node/private-direct.mjs:60Private wake token can be forwarded to an arbitrary caller-supplied endpoint
Referenced artifact was not completely inspected
re, timestamp, unknown key, tampered target, and atomic nonce replay; then run `conformance-direct.mjs`. If the database cannot atomically consume a nonce, stop
Referenced artifact was not completely inspected
Use [scripts/bellwire.mjs](scripts/bellwire.mjs) for API operations. It defaults to the official hosted API and accepts `BELLWIRE_API_URL` for self-hosted insta
Referenced artifact was not completely inspected
- Read [adapters.md](references/adapters.md) for Node.js, Cloudflare Worker, Shell, and GitHub Actions patterns.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
file after successful import.
- Give each project its own mode-specific runtime token. Never reuse a wake or
Ingest Token across repositories.
- Treat email, phone, name, IP address, customer ID, access token, and free-form user content as sensitive unless the user says otherwise.
- Private is the default. Bellwire receives only an encrypted connection
envelope and a random opaque wake reference; the App pulls notification,
Inbox, and Surface content from the user's service with a signed request.
The skill instructs the agent to access environment secrets and perform networked API operations, but it does not declare an explicit tool/permission scope such as allowed-tools or permissions. This creates an authority mismatch: a caller cannot easily tell that the skill may read secrets and make external requests, increasing the risk of unintended secret exposure or unauthorized outbound actions if the skill is invoked in a permissive runtime.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
await fetch(
`https://api.bellwire.app/v1/projects/${projectId}/private-wakes`,
{
method: "POST",
signal: AbortSignal.timeout(5_000),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
await fetch(
`https://api.bellwire.app/v1/projects/${projectId}/private-wakes`,
{
method: "POST",
signal: AbortSignal.timeout(5_000),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
await fetch(
`https://api.bellwire.app/v1/projects/${projectId}/private-wakes`,
{
method: "POST",
signal: AbortSignal.timeout(5_000),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
await fetch(
`https://api.bellwire.app/v1/projects/${projectId}/private-wakes`,
{
method: "POST",
signal: AbortSignal.timeout(5_000),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl --fail-with-body --silent --show-error \
--max-time 5 \
--request POST \
--header "Authorization: Bearer ${BELLWIRE_INGEST_TOKEN:?missing}" \
Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
2. Verify the signature and timestamp before parsing or trusting any field.
3. Return a stable provider event ID and provider event time.
4. Reject invalid signatures without calling Bellwire.
5. Ignore unsupported event types with a successful response so providers do not retry forever.
Use the provider's official verification library when the project already uses
it or when the signature algorithm is easy to implement incorrectly. Never
The function performs a network POST to an external Bellwire API and includes a bearer token in the Authorization header. Although the function name and code make the purpose clear to a developer, this file does not include any user-facing warning, prompt, or disclosure comment that the skill transmits data and credentials off-host.
Detected: suspicious.env_credential_access