enrichment-playbook

Enrich software package artifacts with vulnerability and reversing analysis data.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill enrichment-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enrichment-playbook
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/secure-software/skills/enrichment-playbook
Command: npx skills add https://github.com/dreadnode/capabilities --skill enrichment-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security analysts and supply chain teams often waste hours manually gathering scattered security and reversing signals from software package artifacts, leading to missed risks and inconsistent analysis results.

Core Features & Use Cases

  • Multi-stage artifact triage: Automates archive extraction, per-file hashing, string extraction, entropy calculation, and YARA rule scanning to surface hidden risks like obfuscated code, packed binaries, and malicious patterns.
  • External vulnerability enrichment: Integrates OSV, Scorecard, and Spectra Assure data to link package artifacts to known CVEs, supply chain weaknesses, and third-party security assessments.
  • Use Case: A red teamer evaluating a suspicious downloaded Python package can use this Skill to automatically extract all files, scan for base64-encoded payloads and eval chains, pull associated OSV vulnerability records, and hand off any native binaries to specialized reversing tools for deeper analysis.

Quick Start

Use the enrichment-playbook skill to deep scan the downloaded package file 'third-party-lib-v2.1.0.zip' and generate a summary of all identified risks, vulnerability matches, and files that require further reversing analysis.

Frequently Asked Questions about enrichment-playbook

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

FAQPage Schema
How do I automate security enrichment and vulnerability scanning for downloaded software packages?

Automate security enrichment by extracting archives, hashing files, scanning with YARA rules, and querying OSV data to surface malicious code and vulnerabilities in software packages. This eliminates manual signal gathering and standardizes triage.

What is the best way to scan a suspicious Python package for obfuscated payloads and known CVEs?

Scan suspicious Python packages by calculating file entropy, extracting strings to find base64-encoded payloads, and matching artifacts against OSV vulnerability records to identify supply chain risks. This process reveals hidden malicious patterns automatically.

Can I use YARA rules to detect malicious patterns inside extracted archive files?

Yes, YARA rule scanning is applied to extracted archive files to detect obfuscated code, packed binaries, and malicious patterns during the package enrichment process. This helps security analysts identify hidden risks in third-party dependencies.

Does this package analysis workflow support reversing native binaries and web assembly modules?

Yes, the package analysis workflow supports handoff to language-specific reversing toolchains for .NET, native binaries, and web assembly modules after initial triage. This allows deeper analysis of suspicious compiled code found within packages.

How do I link third-party dependencies to supply chain weaknesses and security assessments?

Link third-party dependencies to supply chain weaknesses by integrating OSV, Scorecard, and Spectra Assure data during the artifact enrichment process. This automatically maps downloaded files to known vulnerabilities and external security posture evaluations.

When should I use entropy calculation and string extraction during package reversing?

Use entropy calculation and string extraction during package reversing to identify packed binaries, obfuscated code, and suspicious eval chains in downloaded artifacts. These multi-stage triage steps surface hidden risks before deeper manual analysis begins.