mandiant / mandiant/VM-Packages
Add Deobfuscation Category & Tools
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 246
- Forks
- 98
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 7
Description
### Details
Modern malware is increasingly becoming more complex and obfuscated, thus I think it is worthwhile to include tools/libraries to assist with general deobfuscation of executables, outside of the standard .NET deobfuscation and javascript deobfuscation tools we have.
Example List for PE files:
- d810 and/or d810-ng (https://github.com/joydo/d810 / https://github.com/w00tzenheimer/d810-ng)
- z3 (https://github.com/z3prover/z3)
- cvc5 (https://github.com/cvc5/cvc5)
- klee (https://github.com/klee/klee)
- triton (https://github.com/jonathansalwan/triton)
- gooMBA (https://github.com/HexRaysSA/goomba)
- Miasm (https://github.com/cea-sec/miasm)
Example list for additional javascript tools:
- restringer (https://github.com/HumanSecurity/restringer)
- synchrony (https://github.com/relative/synchrony)
- webcrack - (https://github.com/j4k0xb/webcrack)
- jsir (https://github.com/google/jsir)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing .NET and JavaScript deobfuscation categories and their package definitions. Review the listed PE and JavaScript tools against the repository's packaging conventions; done means the new deobfuscation category and appropriate tool packages are represented consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- reverse-engineering, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100