moyun-ultimate/skills/threat-hunting/SKILL.md
moyun-ultimate 24db9f592e feat: moyun-ultimate 0.1.0 — five-layer fused jailbreak core
Merge 12 community jailbreak packages into one layered plugin instead of
stacking them (stacking makes them fight over the same host targets).

Layers:
- order 100 persona core (moyun-banzhuan, text verbatim)
- order 150 refusal kernel (dsh-po: authorization-as-given, foreign-pattern table)
- order 160 execution intensity (dsh-unrestricted + arsenal execution_mode)
- order 200 anti-dilution mirror
- order 210 skill routing (63 skills, synced idempotently into $DSH_HOME/skills)

Tools: moyun_frame (5 re-framing templates on demand), moyun_ultimate_profile.
Client: live refusal-score badge.

Ships no host source patches, so it never fights dsh-purge; the permission
layer stays with dsh-purge.
2026-11-16 13:37:04 +08:00

2.0 KiB
Raw Blame History

name description
threat-hunting Use for blue-team threat hunting, detection engineering with Sigma/YARA, SIEM query design, and incident detection validation.

Threat Hunting & Detection Engineering

ACTION REQUIRED(读完后立刻执行)

  1. NOW: 确认蓝队/狩猎授权与数据源范围(SIEM、EDR 导出)
  2. NOW: 明确假说(hypothesis)再查数,避免无脑刷告警
  3. NEXT: 工具与数据接入方式
  4. ACT: 假说 → 查询 → 验证 → 规则化

适用场景

  • 威胁狩猎(hypothesis-driven)
  • Sigma / YARA 检测工程
  • 告警调优、误报分析
  • 与 malware-analysis/:样本侧 IOC → 本 skill 落地检测
  • 与 digital-forensics/:案件伪影 → 横向狩猎

工作流

1. 建假说

例:攻击者用 living-off-the-land 做横向
→ 数据源:Sysmon 1/3/10、Windows Security 4624/4648
→ 成功标准:发现异常父进程或罕见账户日志源

2. 查询与堆叠

□ 基线:正常管理员行为时段与主机
□ 异常:新服务、编码 PowerShell、异常出站
□ 关联:同账号多主机短时登录

3. 规则化

# Sigma 骨架见 malware-analysis;本 skill 强调:
# - 误报面
# - 数据源字段映射
# - 响应 playbook 链接

4. 验证

□ 原子测试(Atomic Red Team)仅在授权实验室
□ 回放历史日志验证召回

工具链

工具 用途
Sigma CLI / sigmac 规则转换
YARA 文件/内存
SIEM(ELK/Splunk 等) 查询
osquery 端点狩猎
Atomic Red Team 检测验证(实验室)

参考

  • references/hunting-loop.md
  • ../malware-analysis/references/yara-sigma-rules.md
  • ../digital-forensics/

路由上下文

上游: MASTER R27
下游: 确认入侵 → forensics;恶意样本 → malware-analysis
MUST NOT: 在无授权生产环境跑攻击模拟

任务完成自检

  • 是否有明确假说与结论?
  • 规则是否注明误报与数据源?
  • Checklist?