UTC: 2025-04-20 06:01
virtualex-itv/chocolatey-packages
This file is automatically generated by the update_all.ps1 script using the Chocolatey-AU module.
Ignored | History | Force Test | [Rele
#!/usr/bin/env python3 | |
# | |
# Author: @jaydinbas | |
# | |
# Extract config from Knotweed Jumplump samples | |
# Note: Not all samples tagged as 'Jumplump' in the MS report | |
# contain a config, some just load other samples that do | |
# | |
# Works for | |
# cbae79f66f724e0fe1705d6b5db3cc8a4e89f6bdf4c37004aa1d45eeab26e84b |
UTC: 2025-04-20 06:01
virtualex-itv/chocolatey-packages
This file is automatically generated by the update_all.ps1 script using the Chocolatey-AU module.
Ignored | History | Force Test | [Rele
I've shared this technique with some people privately, but might as well share it publicly now since I was asked about it. I've been using this for a while now with good success. It works well for parsing .NET droppers and other things.
If you don't know what the -D flag to YARA does I suggest you import a module and run a file through using that flag. It will print, to stdout, everything the module parsed that doesn't involve you calling a function. This is a great way to get a quick idea for the structure of a file.
For example:
wxs@mbp yara % cat always_false.yara
This Gist has been transfered into a Github Repo. You'll find the most recent version here.
When creating your rules for YARA keep in mind the following guidelines in order to get the best performance from them. This guide is based on ideas and recommendations by Victor M. Alvarez and WXS.