wrdn-data-exfil

Trace untrusted input from sources to sinks to identify data-exfiltration bugs.

Updated Aug 3, 2025
One-click install
npx skills add https://github.com/cschmatzler/nixos-config --skill wrdn-data-exfil-cschmatzler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrdn-data-exfil
Source: https://github.com/cschmatzler/nixos-config/tree/main/modules/_pi/skills/warden-skills/wrdn-data-exfil
Command: npx skills add https://github.com/cschmatzler/nixos-config --skill wrdn-data-exfil-cschmatzler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps security engineers identify and piece together data-leak paths from untrusted inputs to data sinks.

Core Features & Use Cases

  • Trace sources and sinks across code paths and libraries to reveal exfiltration vectors.
  • Analyze diffs touching HTTP clients, file I/O, raw queries, XML parsing, and exports to map data flow end-to-end.
  • Apply framework-specific references to validate and remediate leakage scenarios.

Quick Start

Trace a diff touching HTTP clients, file I/O, or export pipelines to map an untrusted data flow from source to sink.

Frequently Asked Questions about wrdn-data-exfil

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect data-exfiltration paths from untrusted input in a code diff?

Detect data-exfiltration paths by tracing untrusted input from sources to sinks across HTTP clients, file I/O, raw queries, and export pipelines. Analyzing code diffs maps the end-to-end data flow to reveal potential leakage vectors.

What is a data-leak path between a source and a sink?

A data-leak path connects untrusted input sources to data exfiltration sinks. Tracing this path across code libraries and frameworks identifies how malicious data flows to HTTP clients, raw queries, or XML parsing endpoints.

How do I trace untrusted data flow across HTTP clients and file I/O operations?

Trace untrusted data flow across HTTP clients and file I/O by analyzing code diffs to map the source-to-sink path. Applying framework-specific guidance validates how data moves through response serializers and error handlers.

Does this data-exfiltration analysis work with framework-agnostic codebases?

Yes, this data-exfiltration analysis is framework-agnostic. It traces untrusted inputs to sinks using included references for data-leak patterns and framework-specific guidance to validate leakage scenarios across varied libraries.

Can I analyze raw queries and XML parsing for data leakage in code diffs?

Yes, you can analyze raw queries and XML parsing for data leakage. The analysis scope explicitly covers tracing untrusted input through these sinks within code diffs to identify exfiltration vulnerabilities.

What are the limitations of tracing data-exfiltration paths using code diffs?

Tracing data-exfiltration paths is limited to the scope of provided code diffs. Analysis requires diffs touching HTTP clients, file I/O, raw queries, XML parsing, response serializers, error handlers, or export pipelines to map data flow.