Back to skill

Security audit

DwC Check

Security checks for vulnerabilities and agentic risk

Overview

The scanners report a benign skill with medium confidence: they found no AIG issues, and the one install-command match was judged expected for its stated purpose, though the review was partial.

The verdict is benign, but confidence is medium and the scan is partial: a local path-like reference was unresolved. Before installing, consider checking the linked project and its install instructions, and whether you trust that source.

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
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

YARA rule 'agent_skill_remote_bootstrap_execution': Remote script or code download followed by execution/bootstrap installation [agent_skills]

High
Category
YARA Match
Confidence
85% confidence
Finding

YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).

Content

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

whether country and countryCode agree. Every per-record finding is reported under the same flag GBIF itself would use (for example COORDINATE_INVALID, ZERO_COORDINATE, BASIS_OF_RECORD_INVALID, COUNTRY_MISMATCH), with the row and term, so the file can be fixed before the real GBIF validator ever sees it. It only reads the file; it never uploads or changes anything.

Install

bash
pip install git+https://github.com/RakTikoo/dwccheck

This provides the dwccheck command.

Run

Check one occurrence file:

bash
dwccheck check occurrences.csv

The same findings in machine-readable form come from --format json or --format csv (one finding per object or row: row, flag, severity, term, value, message). A .txt input has its delimiter sniffed from its first line. To see every flag the tool can emit, with GBIF's definition of each:

bash
dwccheck flags

Reading the results

Findings print one per line: row N: FLAG [term] — message for record pro