analyzing-supply-chain-malware-artifacts

Featured

Investigate supply chain attack artifacts including trojanized software updates, compromised build pipelines, and sideloaded dependencies to identify intrusion vectors and scope of compromise.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Analyzing Supply Chain Malware Artifacts ## Overview Supply chain attacks compromise legitimate software distribution channels to deliver malware through trusted update mechanisms. Notable examples include SolarWinds SUNBURST (2020, affecting 18,000+ customers), 3CX SmoothOperator (2023, a cascading supply chain attack originating from Trading Technologies), and numerous npm/PyPI package poisoning campaigns. Analysis involves comparing trojanized binaries against legitimate versions, identifying injected code in build artifacts, examining code signing anomalies, and tracing the infection chain from initial compromise through payload delivery. As of 2025, supply chain attacks account for 30% of all breaches, a 100% increase from prior years. ## When to Use - When investigating security incidents that require analyzing supply chain malware artifacts - When building detection rules or threat hunting queries for this domain - When SOC analysts need structured procedures for this analysis type - When validating security monitoring coverage for related attack techniques ## Prerequisites - Python 3.9+ with `pefile`, `ssdeep`, `hashlib` - Binary diff tools (BinDiff, Diaphora) - Code signing verification tools (sigcheck, codesign) - Software composition analysis (SCA) tools - Access to legitimate software versions for comparison - Package repository monitoring (npm, PyPI, NuGet) ## Workflow ### Step 1: Binary Comparison Analysis ```python #!/usr/bin/env python3 """Compare ...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

offensive-supply-chain

Comprehensive offensive methodology for software supply chain attacks covering the full kill chain from reconnaissance through exploitation. Addresses dependency confusion across npm, PyPI, and NuGet ecosystems where internal registry override allows an attacker to inject malicious packages that shadow private dependencies. Covers typosquatting techniques for popular packages, compromised package injection via maintainer account takeover or social engineering, and build system attacks through Makefile injection, setup.py install hooks, and npm postinstall scripts. Extends into CI/CD artifact tampering where build outputs are replaced or modified in transit, code signing abuse through stolen or self-signed certificates, upstream repository compromise via commit injection or force-push to trusted repos, and container image supply chain attacks including base image trojaning and registry confusion. Maps to MITRE ATT&CK T1195.001 (Supply Chain Compromise: Compromise Software Dependencies and Development Tools) an

11,204 Updated yesterday
SnailSploit
AI & Automation Listed

detect-supply-chain-compromise

Detection and response for supply-chain compromise: a poisoned software package or tampered build artifact that executes on install (MITRE ATT&CK T1195.002, T1546 for .pth / import-hook persistence, T1552 for credential stealers), and a trusted MSP or RMM platform turned into a delivery channel (T1199, T1543.003, T1572). Keyed off Linux file-creation telemetry (auditd, Sysmon for Linux, EDR) over site-packages, Windows System Event ID 7045, Windows process creation (Sysmon 1 / Security 4688), and package and container inventory. Ships two UMBRASEC sigma-pack rules plus a hunt, with tuning and Essential Eight / ISO 27001 / NIST CSF 2.0 mappings. Use when a dependency or Docker image you run was backdoored, triaging a PyPI, npm, or container supply-chain advisory, hunting a cook.pth import hook or dropped credential stealer, responding to an MSP or RMM compromise, or chasing an unexpected Cloudflared tunnel service.

0 Updated 5 days ago
umbrasec-labs
AI & Automation Featured

hunting-for-supply-chain-compromise

Hunt for supply chain compromise indicators including trojanized software updates, compromised dependencies, unauthorized code modifications, and tampered build artifacts.

36,355 Updated 2 months ago
mukul975