mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
60 lines
2.6 KiB
Markdown
60 lines
2.6 KiB
Markdown
---
|
|
name: performing-supply-chain-attack-simulation
|
|
description: Simulate and detect software supply chain attacks including typosquatting detection via Levenshtein distance,
|
|
dependency confusion testing against private registries, package hash verification with pip, and known vulnerability scanning
|
|
with pip-audit.
|
|
domain: cybersecurity
|
|
subdomain: application-security
|
|
tags:
|
|
- supply-chain
|
|
- typosquatting
|
|
- dependency-confusion
|
|
- package-verification
|
|
- pip-audit
|
|
- PyPI
|
|
- software-composition-analysis
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.PS-01
|
|
- PR.PS-04
|
|
- ID.RA-01
|
|
- PR.DS-10
|
|
---
|
|
|
|
# Performing Supply Chain Attack Simulation
|
|
|
|
## Overview
|
|
|
|
Software supply chain attacks exploit trust in package registries through typosquatting (registering names similar to popular packages), dependency confusion (publishing higher-version public packages matching private names), and compromised package distribution. This skill detects these attack vectors by computing Levenshtein distance between package names and popular PyPI packages, verifying package integrity via SHA-256 hash comparison, scanning for known CVEs with pip-audit, and testing dependency resolution order for confusion vulnerabilities.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When conducting security assessments that involve performing supply chain attack simulation
|
|
- When following incident response procedures for related security events
|
|
- When performing scheduled security testing or auditing activities
|
|
- When validating security controls through hands-on testing
|
|
|
|
## Prerequisites
|
|
|
|
- Python 3.9+ with `pip-audit`, `Levenshtein`, `requests`
|
|
- Access to PyPI JSON API (https://pypi.org/pypi/{package}/json)
|
|
- Network access for package metadata retrieval
|
|
|
|
|
|
> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.
|
|
|
|
## Key Detection Areas
|
|
|
|
1. **Typosquatting** — compare package names against top PyPI packages using edit distance thresholds
|
|
2. **Dependency confusion** — check if internal package names exist on public PyPI with higher version numbers
|
|
3. **Hash verification** — download packages and verify SHA-256 digests match published hashes
|
|
4. **Vulnerability scanning** — audit installed packages against OSV and PyPA advisory databases
|
|
5. **Metadata anomalies** — flag packages with suspicious author emails, missing homepages, or very recent first upload dates
|
|
|
|
## Output
|
|
|
|
JSON report with risk scores per package, detected attack vectors, hash verification results, and CVE findings.
|