mandiant / mandiant/capa-rules

Detect Cuckoo SandBox

Open
#327 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

FLARE-TODO rule idea
Dominant language
No language data
Stars
736
Forks
245
Avg merge
4d 53m
Merged PRs (30d)
2

Description

## Summary

Modify and add new rules to `anti-analysis/anti-vm/vm-detection` to detect sandboxes detection/evasion focusing on techniques used to detect/evade Cuckoo.

## Possible test samples

Publicly available samples that may contain the capability this rule should detect (MD5 hashes):
- 4d7420cc69753f31a946a4e86db0b2ca
- fccaaab898715da863f24ba4a15656e8
- d8a06811385e0fd463f215a43b366169

## References

Links or references to additional information on the capability (can also be included in the rule):

- https://cuckoosandbox.org/
- https://www.ptsecurity.com/ww-en/analytics/antisandbox-techniques
- https://blog.checkpoint.com/wp-content/uploads/2016/10/DefeatingSandBoxEvasion-VB2016_CheckPoint.pdf

## Namespace

Proposed namespace: `anti-analysis/anti-vm/vm-detection`. More details in https://github.com/fireeye/capa-rules/blob/master/doc/format.md#rule-namespace

## att&ck

`aka.mitre.att&ck.t1497.001`

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing rules under anti-analysis/anti-vm/vm-detection and the rule format documentation linked in the issue. Review the listed sample hashes and the Cuckoo and anti-sandbox references to identify the intended detection behavior. Done means adding or modifying rules in the proposed namespace with coverage for the relevant Cuckoo sandbox detection or evasion techniques.

Written by the indexing model from the issue text.

Assessment

Domain
reverse-engineering, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.