Detection proposal: VBA Stomping (T1564.007) - EvilClippy execution and vbaProject.bin creation by non-Office process

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

维护者通常 1 天内回复

@ali-vrd 已经在做这个了。

开始于 2026年11月10日。

  • #4406 来自 @ali-vrd —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
backend, security

调研方向

Start by checking the detection conventions under detections/ on develop and the equivalent SigmaHQ proposal, then identify the ESCU format and review process for new detections. The issue specifies two analytics: EvilClippy process execution and non-Office, non-archiver creation of vbaProject.bin. Done means submitting both SPL detections with naming, status, and analytic story placement aligned to maintainer guidance; attack data and tests need maintainer direction.

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

描述

Hi team! 👋

I would like to contribute two new detections for VBA Stomping (T1564.007, Defense Evasion). As of today ESCU has no detection covering this technique (verified against detections/ on develop).

Background: VBA stomping removes the VBA source code from an Office document while keeping the compiled p-code, so the macro still executes but the malicious source is invisible to static analysis tools and even the VBA editor. EvilClippy (Outflank) is the best-known open-source tool implementing this technique. MITRE reference: https://attack.mitre.org/techniques/T1564/007/

Proposed detections:

  1. EvilClippy execution - Endpoint.Processes datamodel, process_name/original_file_name = EvilClippy.exe (Sysmon EID 1 / Security 4688 / EDR telemetry)
  2. vbaProject.bin creation by a non-Office process - Endpoint.Filesystem datamodel, file_name = vbaProject.bin where the creating process is NOT an Office application (WINWORD/EXCEL/POWERPNT/MSACCESS/OUTLOOK/...) and not a common archiver (7z, WinRAR, Bandizip), since a legitimately saved macro project is always written by the Office host process (Sysmon EID 11)

Prior art: I have just submitted equivalent coverage to SigmaHQ (SigmaHQ/sigma#6595) and would love to port it to SPL for ESCU.

Attack data: I could not find EvilClippy or vbaProject datasets in splunk/attack_data, so the initial PR will not include unit tests. I am happy to help record/generate attack data if maintainers point me to the preferred process, or the team can generate it with attack_range as usual.

CLA: I am completing the individual contributor agreement now and will confirm it in the PR.

Happy to adjust naming, status, and analytic story placement per maintainer feedback. Thanks!

主要语言
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 摘要。