Detection proposal: Chromium remote debugging used for cookie theft

未关闭
#4,389 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
security

调研方向

Start with the existing Headless Browser Usage analytic, which the issue says misses remote-debugging launches, and the Phemedrone Stealer story where the new analytics would go. Build the two proposed detections, one Anomaly on browser processes with a remote-debugging switch and one Hunting search on Sysmon EID 3 loopback connections to ports 9222-9229, then run contentctl-ng build. Done means the build passes and both analytics fire on the lab cases while staying silent on the negatives.

由索引模型根据 Issue 内容生成。

描述

enhancement

Gap. After Chrome's App-Bound Encryption, infostealers (for example Phemedrone, per Elastic Security Labs) launch Chrome or Edge with --remote-debugging-port or --remote-debugging-pipe and a non-default --user-data-dir. They then read cookies through the DevTools Protocol, often headless or with the window placed off-screen. security_content has no analytic for --remote-debugging. The existing Headless Browser Usage analytic requires --headless AND --disable-gpu, and in my lab it missed every remote-debugging launch.

Proposal.

  • Windows Chromium Browser Remote Debugging Enabled (Anomaly, Endpoint.Processes): browser main processes (Chrome, Edge, Brave, Opera, Vivaldi) started with a remote-debugging switch. Child processes and the elevated self-relaunch are excluded. Triage fields: debug_mode (fixed port, port 0, pipe), alt_profile and hidden.
  • Windows Local Chromium DevTools Port Connection By Non-Browser Process (Hunting, Sysmon EID 3): a non-browser process initiating a loopback connection to ports 9222-9229.

Both would go under the existing Phemedrone Stealer story (T1539, T1185).

Evidence. Native Windows 11 with Edge 156, Chrome 156 and Sysmon 15.22, using empty temporary profiles. The DevTools endpoint answered on all three fixed-port cases. Results: Anomaly 5/5 with no hits on 2 negatives; Hunting 1/1. contentctl-ng build passes. Related: #4382, #4383 and the dMSA proposal.

主要语言
Python
星标
1.7k
派生
507
平均合并
3 天 18 小时
30 天内合并 PR
36

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

splunk/security_content 的其他 Issue

查看 splunk/security_content 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。