-
Notifications
You must be signed in to change notification settings - Fork 153
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
Windows 10 #64
Comments
I haven't tested a full setup, but I have tested capemon and the new loader on Windows 10. It seems to inject into processes no problem, although loading a new process seems not to load a window for something like notepad so there are perhaps issues to iron out there, but still the process runs and the monitor loads. Definitely something I want to be compatible with so I will need to test it further. |
Thanks. I'll build one and see how it goes. |
Great - let me know. Be sure to try the new loader by renaming newloader* to loader* in the bin folder! |
I forgot there is actually a branch for testing the new loader! |
im gonna also try it :) thanks |
hey from my previos tests when we added fixes to dll, and i just tested new loader again, im having the same issue, no behavior on win7
it happens with pe and doc, not tested more formats, example of this one b573b6c322719046af76b16604d77576a741e2809f52bf78f855f1d1623a3f39, doc any idea? i got newloader.exe and placed it instead of loader.exe(renamed obviosly) |
I am curious if Windows 10 x64 is supported now? |
Add in some bootkit/rootkit drive access anomalies
I found that the trick to getting Windows 10 x64 VM working under CAPE is to make sure UAC is fully disabled in the registry:
Also it is good to disable Windows Defender and Real-time Protection from Group Policy. Aside from this, I see no issues with using Windows 10 x64 as the guest. |
The issue currently is more around the question: do the samples detonate properly? Is the API hookng stable? I'm not sure about either of these. For example, try this Trickbot sample, known to run on Win 10: (AnyRun: https://app.any.run/tasks/b0beb3db-1a7c-4e05-9ffd-e3ef278b8877) I'd be interested to hear if you see this running properly in cape with spawned processes and full behaviour. |
Not sure if a 59 second analysis can be considered successful or not. But that is how long it took to run. Here is my html report for that trickbot: Here is the same trickbot analysis with Timeout Enforced to 10 minutes: |
Check the process tree in the any run job. It spawns loads. In cape there is no spawned processes. |
Nope...I definitely see your point. Any ideas of why that is? 64bit vs 32bit? |
Windows 10 largely works now - there will still be issues but they can be created individually when they arise. |
Is this with https://github.com/ctxis/capemon this monitor? |
Any consideration for a Windows 10 capable cuckoomon?
The text was updated successfully, but these errors were encountered: