-
Notifications
You must be signed in to change notification settings - Fork 196
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
New Target - SoftPerfect Nework Scanner 'Netscan' #998
Conversation
Thoughts on adding |
lint fixes
We've come across numerous cases where threat actors simply drop a portable Netscan tool into any accessible folder, such as ProgramData, Perflogs, Music, Documents, Downloads, and so on. I think it would be more efficient to search for this file recursively across the filesystem, considering its potential spread. Another question: For example, an attacker might rename the netscan.xml file to something else. To mitigate this, it would be useful to locate any .xml files within folders whose names contain "Netscan" or "SoftPerfect." Essentially, the search pattern would look something like this: Let me know if this is feasible or if there’s a workaround! |
Honestly, great question! I am unsure if regex can be leveraged within |
no, not path, just the filename. if you want recursive, its gonna be a walk of everything OR you pull the MFT via kape and then look thru the csv |
another pivot is prefetch, and narrowing down the path from there |
Thank you for your response. Can we at least merge to implement the search specifically for the netscan.xml file? |
yea @AndrewRathbun can verify that all looks good |
Description
This target will fetch the default output of the network scanning tool "Netscan".
This tool is frequently observed in cases where threat actors neglect to delete its output.
Since this file contains valuable information, such as previously compromised hosts and the credentials used, it enables us to rapidly identify the compromised scope.
Checklist:
GUID
for my Target(s)/Module(s)Misc
folder or created a relevant subfolder with justification--tlist
/--mlist
and corrected any errorsN/A
underneath the Documentation header