GitHub Actions Cache Native Malware - for Educational and Research Purposes only.
-
Updated
May 8, 2026 - TypeScript
GitHub Actions Cache Native Malware - for Educational and Research Purposes only.
A python tool to test for web cache poisoning denial of service (CPDoS) vulnerabilities.
A high-accuracy, behavioral cache poisoning scanner for modern Web APIs
Compliance evidence for HTTP header security. Assesses both sides of the exchange — the request headers an attacker manipulates and the response headers you must send — confirms every finding with a second probe, maps it to OWASP ASVS 5.0 and PCI DSS 4.0.1, and reports what it could not assess instead of counting it as a pass.
Lightweight CLI tool for testing web cache deception vulnerabilities. Built to avoid manual testing, bloated recon tools, and GUI-based platforms. Simple, fast, and script-friendly.
Modern Topics In Network Security Lab reports (including screenshots of server configuration, iptables rules, fail2ban configurations and BIND DNS server implementation). Additionally python code to implement port scanning , DOS attack and DNS cache poisoning attack is included.
PoC for Cache Poisoning Attack over DNS (DNS Spoofing)
☠️ DNS poisoning attack toolkit | Cache poisoning, spoofing | NullSec Framework | @anonantics
8-phase cache & transport attack scanner — cache poison, request smuggling, H2C, CDN bypass
C++ DNS cache inspector for poisoning and anomaly detection
A red-team lab for the MCP discovery surface: instructions-field prompt injection, cacheScope:public cross-caller cache poisoning, and post-approval drift, with four controls that stop them.
t3stc4ch3.py is a tool designed to test if URLs are being cached.
Demonstrated DNS spoofing and DNS cache poisoning attacks in a controlled lab environment using Scapy and Python. Manipulated DNS responses, injected forged authority and additional records, poisoned DNS caches, and analyzed DNS server behavior during name resolution attacks.
Unkeyed Header Cache Poisoning Probe and PoC Builder
To associate your repository with the cache-poisoning topic, visit your repo's landing page and select "manage topics."