![]() |
|
Forensics WorkShop Part 2 - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45) +--- Forum: Grayhat • Purple Team • Hybrid Security (https://hackforums.net/forumdisplay.php?fid=449) +---- Forum: Beginner Hacking (https://hackforums.net/forumdisplay.php?fid=4) +---- Thread: Forensics WorkShop Part 2 (/showthread.php?tid=5858506) |
Forensics WorkShop Part 2 - CyberStrike - Jul 6, 2018 Foreword: I encourage everyone to participate, whether or not you have done this before or not, hands on is the best way to learn and I have included resources on volatility, which is a commonly used memory forensics framework. The solution will be posted on Monday, as to give everyone enough time to work on this challenge. If you can answer some questions great, if you can complete the whole challenge even better. For an example of the write up, using pastebin for large blocks of text is fine and encouraged. https://hackforums.net/showthread.php?tid=5809120&pid=56810368#pid56810368 Quote:Tools: Volatility or Rekall whois reglookup autopsy/foremost Yara sha256sum strings VirusTotal Once again no need for Kali/Caine/Deft/SANS Sift of course if you want you can use whatever you want. Scenario: A friend from another country is a well known journalist, who writes articles exposing government corruption and civil rights abuses, unfortunately they have reason to suspect that they may have been infected by a malware from a government entity. and she needs your help. Image Download: http://www.mediafire.com/file/yxqodp1p2aca91x/0zapftis.rar Password: infected RAR sha256sum: 0ab81aec6d61593a03a7b6fbda9266af8dd9c8df1b6477faa880fafd19cb21b1 0zapftis.rar Extracted File Type: vmem Quote:Resources: https://github.com/volatilityfoundation/volatility/wiki https://resources.infosecinstitute.com/memory-forensics-and-analysis-using-volatility/ https://github.com/volatilityfoundation/volatility/wiki/Command-Reference Common Malware Registry locations: https://resources.infosecinstitute.com/common-malware-persistence-mechanisms/ Yara Rules: https://github.com/Yara-Rules/rules Quote:Questions: Edit: Something I wanted to add, is that by understanding how a defender defends you can be a better attacker. For example you have to know what AV and figure out a way of bypassing that AV, the same principal here seeing how other attackers do their work will give you an idea of different tactics and techniques. Also seeing what an analyst can pick out of just a memory dump of a machine, which is what this is just a snapshot of a compromised machine, it can give you a better idea on how to avoid or hamper an analyst when they are looking at a machine you have compromised. So this is not just a look at a defender's toolset instead you can use it to further your attacks, and be more aware of what is left behind after an attack. RE: Forensics WorkShop Part 2 - 0riginalkillit - Jul 6, 2018 Buddy I am really new to this but I am interested in learning this.but I will give it a try and thank you for the resources I never knew about that except kali--->but kali freezes sometimes while working so I will give it a try RE: Forensics WorkShop Part 2 - ItsJigSaw - Jul 6, 2018 Feelsbad i wont be home untill monday evening. Will check the results tho, rly interested. Great post. RE: Forensics WorkShop Part 2 - CyberStrike - Jul 6, 2018 Give it a shot ItsJigSaw, even if it is solved you can use the solutions if you get stuck. 0riginalkillit, interesting what graphics card do you got in that machine? Also is it VM or installed to HD? RE: Forensics WorkShop Part 2 - Fred213 - Jul 7, 2018 (Jul 6, 2018 10:25 AM)ItsJigSaw Wrote: Feelsbad i wont be home untill monday evening. Will check the results tho, rly interested. CAN YOU PLZ REPLY MY MSG? RE: Forensics WorkShop Part 2 - CyberStrike - Jul 7, 2018 Alright just finished had multiple interruptions tonight, took about 6 hours to finish, solution will be posted on Monday. If someone get's stuck post here we can all help one other out. RE: Forensics WorkShop Part 2 - ItsJigSaw - Jul 7, 2018 (Jul 7, 2018 02:35 AM)Fred213 Wrote: CAN YOU PLZ REPLY MY MSG? I dont have a msg from u in my inbox. RE: Forensics WorkShop Part 2 - CyberStrike - Jul 8, 2018 If anyone needs help, get's stuck, even wants more resources so they can attempt the challenge on their time feel free to post I'll be more than happy to help. RE: Forensics WorkShop Part 2 - 0riginalkillit - Jul 8, 2018 (Jul 8, 2018 04:53 AM)sirru5h Wrote: If anyone needs help, get's stuck, even wants more resources so they can attempt the challenge on their time feel free to post I'll be more than happy to help. Great thank for fixing the links all links are 100% working 🤝 RE: Forensics WorkShop Part 2 - CyberStrike - Jul 8, 2018 (Jul 8, 2018 05:15 AM)0riginalkillit Wrote: Great thank for fixing the links all links are 100% working Excellent I apologize for that, I used links from the first challenge and assumed that they were all working fine, that said if you refer to the first one you will find that this challenge follows much of the first one. RE: Forensics WorkShop Part 2 - CyberStrike - Jul 9, 2018 Complete write up: https://pastebin.com/DgsYHPXi (I included a link to solve the majority of the challenge although a few things we do are a bit more involved) DLL List: https://pastebin.com/JUk8yj3d Filescan: https://pastebin.com/7w6zStHh SVCscan: https://pastebin.com/fEtZcHzd TimeLine of Compromise: https://pastebin.com/FeVaF2Qn PID 1956 ThreadScan: https://pastebin.com/WQDXFjLx RE: Forensics WorkShop Part 2 - 0riginalkillit - Jul 10, 2018 (Jul 9, 2018 06:41 PM)sirru5h Wrote: Complete write up: Thank you buddy I am going through it and I want you to keep that link alive I am using it for a month now to learn Spoiler (Click to View) 🤝 RE: Forensics WorkShop Part 2 - CyberStrike - Jul 10, 2018 (Jul 10, 2018 06:04 AM)0riginalkillit Wrote: Thank you buddy I am going through it and I want you to keep that link alive I am using it for a month now to learn Those links shouldn't expire also I used pastbin for everything due to the amount of text involved. Good luck! |