Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dump binary registry data to file #164

Open
enzok opened this issue Oct 15, 2018 · 4 comments
Open

Dump binary registry data to file #164

enzok opened this issue Oct 15, 2018 · 4 comments

Comments

@enzok
Copy link
Contributor

enzok commented Oct 15, 2018

Malware can write binaries to the registry for persistence, etc. It would be nice to capture the data/binary as either a dropped file or supplementary file. I know the registry API hooks are logging the data, but it's limited to a small buffer currently.

I'd say this is more of a feature request than an issue.

@kevoreilly
Copy link
Contributor

This should be a straightforward addition, a really old package does something like this (EvilGrab) so I will update the code and signatures to a more general feature.

kevoreilly added a commit that referenced this issue Oct 17, 2018
@kevoreilly
Copy link
Contributor

I've created a signature as the first step in building this feature - if you could test it out and make sure it triggers where you expect it to (i.e. whenever a PE image is written to the registry) that would be great. Or if you can supply the hashes, even better. Then I will create a package to dump them out.

enzok pushed a commit to enzok/CAPE that referenced this issue Oct 17, 2018
… written to registry (for ctxis#164)

(cherry picked from commit 3a41983)
@enzok
Copy link
Contributor Author

enzok commented Oct 17, 2018

This will handle PE files nicely. However, there are often times that scripts and config data are also written to the registry. It would be good to handle these instances as well.

I would dump anything with a size greater than 16KB (see creates_largekey.py signature.)

@enzok
Copy link
Contributor Author

enzok commented Oct 17, 2018

Something else to consider, the binary maybe be obfuscated as well.

enzok pushed a commit to enzok/CAPE that referenced this issue Oct 3, 2019
Powershell shadowcopy modification into Curtain
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants