redteam-opsec
Skill19 starsChanged 2 months agoApache-2.0View on GitHub
OPSEC隐蔽作战纪律:IP黑名单绕过,速率时序,流量混淆,最小足迹,反取证,渐进暴露。Use when maintaining stealth, bypassing IP bans, or planning covert red-team ops.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- AIPentest/CyberStrikeAIword for word, first seen Nov 3, 2026
- Ed1s0nZ/CyberStrikeAIword for word, first seen Nov 3, 2026
Other versions2 projects use a version of this.
Word for word · 2
- AIPentest/CyberStrikeAI★ 8.5k100% same
- Ed1s0nZ/CyberStrikeAI★ 8.5k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- active-directory-attackSkill
- ai-llm-app-attackSkill
- attack-surface-reconSkill
- binary-mobile-reversingSkill
- blockchain-contract-attackSkill
- capability-primitive-searchSkill
- cloud-attack-methodsSkill
- component-vuln-intelSkill
- cyberstrike-eino-demoSkill
- experience-closeoutSkill
- handoff-persistence-c2Skill
- initial-access-phishingSkill
- local-corpus-cveSkill
- pentest-agent-osSkill
- pentest-blackboardSkill
- pentest-output-standardsSkill
- pentest-verificationSkill
- post-exploitationSkill
- proxy-tool-bootstrapSkill
- source-code-huntingSkill
- specialized-attack-playbooksSkill
- unlimited-attack-scopeSkill
- web-attack-methodsSkill
- wireless-hardware-attackSkill
- zero-day-discoverySkill
The file
Files
OPSEC / 隐蔽作战纪律（免杀 / 稳定 / 隐蔽）
核心: 打得进 ≠ 打得稳。被发现即行动归零。每个动作执行前先问"这步在防守方眼里长什么样"。
🚨IP黑名单绕过(被ban后第一时间试): X-Forwarded-For: 随机IP (CDN信任此头时直接绕过应用层黑名单,返回code:10010/黑名单时逐个试XFF/X-Real-IP/CF-Connecting-IP/True-Client-IP)
验证: 正常请求返回"黑名单"+你的IP → 加XFF头后返回正常200 → 后续所有请求都带XFF
进阶: 每N个请求换一个XFF值(避免新IP也被ban) | 有些CDN只信任第一个XFF值,有些信最后一个
速率与时序: 扫描限速(nuclei -rl / nmap -T2 --max-rate / ffuf -p延迟)避开WAF封禁+IDS阈值告警 | 高危动作低频+随机jitter | 避业务高峰也避深夜(贴合目标作息最不显眼)
流量混淆: 贴正常业务(常见UA/Referer/合法路径) | 重武器前先探防御(进程列表/已知EDR/SIEM agent特征) → 有则静默手法优先,无监控才上自动化批量
最小足迹: 内存执行优先不落盘(DDexec/memfd/反射加载) | webshell强口令+非常见路径+功能伪装 | 隧道走443/DNS贴常见出站 | 工具用完即删(/dev/shm内存盘,不留残骸)
反取证: 命令历史 unset HISTFILE / set +o history | 日志选择性删自己条目(truncate全清反而触发告警) | 时间戳 touch -r参照邻近文件保persist mtime | 别动监控/审计服务(停了就是告警)
渐进暴露: 被动侦察(证书透明/被动DNS/搜索引擎/资产引擎)→确认无强监控→才主动扫描→最后才上利用落地。能公开情报拿到的绝不主动碰目标。每升一级问"值不值得暴露"。
> 隐蔽不是洁癖,是红队的生存能力。一次莽撞的全端口全速扫描就可能让整个行动归零。Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.