Back to skill

Security audit

didit-event-monitoring

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marks this skill benign with medium confidence: the reported network activity is consistent with event monitoring, though some scanner findings and incomplete coverage warrant care.

The verdict is benign, not risk-free. Before installing, consider whether you trust the Didit events service and are comfortable with the skill using environment credentials and sending event data there. Skillspector inspected only 50% of components, and its tool misuse analysis was degraded, so the evidence is incomplete.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (7)

Tainted flow: 'get_headers()' from os.environ.get (line 64, credential/environment) → requests.post (network output)

Critical
Category
Data Flow
Confidence
90% confidence
Finding

Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.

Content

Scanner excerpt · scripts/send_event.py (reported line 80)May include surrounding context.

python
def post(url: str, payload: dict, ok_statuses: tuple) -> dict:
    r = requests.post(url, headers=get_headers(), json=payload, timeout=30)
    if r.status_code not in ok_statuses:
        print(f"Error {r.status_code}: {r.text}", file=sys.stderr)
        sys.exit(1)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · SKILL.md (reported line 287)May include surrounding context.

md
ubjects/{vendor_data}/?entity_type=company`: one subject's timeline with the same filters. `vendor_data` is unique only within an entity type; omitting `entity_type` returns the `individual` timeline.
- `GET /v3/events/{event_uuid}/`: adds `payload`, `custom_values`, `device_context`, `ip_enrichment`, `subject_profile` (cached email/phone risk signals), `tags`, `field_sources`, and `rule_runs[]` with each run's evidence (`matched_payload`) and the source of each matched field (`server`, `sdk`, `customer`).
- `GET /v3/events/enrichment-metrics/`: `events_ingested`, `enrichment_lookups`, `enrichment_cache_hits`, `enrichment_provider_calls`, `enrichment_skipped_low_value`, `unique_ips_seen`, `cache_hit_rate`, `unique_ip_ratio`, `provider_calls_per_1k_events`, `period_days`. IP enrichment runs once per unique IP, never per event.
- `DELETE /v3/events/{event_uuid}/delete/`: deletes the event (`204`); it is no longer returned by any read. Irreversible. Unknown uuid: `404`.

## Status Values

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: env, network.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 152)May include surrounding context.

Example

bash
curl -X POST https://verification.didit.me/v3/events/ \
  -H "x-api-key: $DIDIT_API_KEY" -H "Content-Type: application/json" \
  -d '{
    "event_id": "login-2026-10-12-000001",

External Transmission

Medium
Category
Data Exfiltration
Confidence
70% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 170)May include surrounding context.

md
import os, requests
from datetime import datetime, timezone

r = requests.post(
    "https://verification.didit.me/v3/events/",
    headers={"x-api-key": os.environ["DIDIT_API_KEY"]},
    json={

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 170)May include surrounding context.

md
import os, requests
from datetime import datetime, timezone

r = requests.post(
    "https://verification.didit.me/v3/events/",
    headers={"x-api-key": os.environ["DIDIT_API_KEY"]},
    json={

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 260)May include surrounding context.

  1. Send from the device: POST https://verification.didit.me/v1/events/ (or /v1/events/batch/) with header X-Monitoring-Token and the same envelope minus subject. The server overwrites subject with the token's binding and derives IP address, user agent and origin from the request; those server values win over client hints. 409 and 200 replay behave as on the server lane.
typescript
const res = await fetch("https://verification.didit.me/v1/events/", {
  method: "POST",
  headers: { "X-Monitoring-Token": monitoringToken, "Content-Type": "application/json" },
  body: JSON.stringify({