TheFatRat is an easy-to-use Exploitation Tool that can help you to generate backdoors and post exploitation attacks like browser attack DLL files. This tool compiles malware with popular payloads and then the compiled malware can be executed on Windows, Linux, Mac OS X and Android.
The malware that is created with this tool also has the ability to bypass most AV software protection.
Features
- Create backdoor for Windows, Linux, Mac OS X and Android
- Bypass antivirus backdoor
- Checks for metasploit service and starts if not present
- Easily craft meterpreter reverse_tcp payloads for Windows, Linux, Mac OS X and Android
- Start multiple meterpreter reverse_tcp listeners
- Fast Search in searchsploit
- Bypass AV
- File pumper
- Create backdoor with another technique
- Autorunscript for listeners (easy to use)
- Drop into Msfconsole
Getting Started
|
1 2 3 |
git clone https://github.com/Screetsec/TheFatRat.git cd TheFatRat chmod +x setup.sh && ./setup.sh |
You can download TheFatRat here:
Or read more here.
By default S3 buckets are not public.
They used to be IIRC, but I could be wrong, well I guess more accurately the easiest way to get access to it programmatically is just to set it to public.
Yes, it had to be configured to be open to the web. This story is not really about AWS. It’s about bad IT controls and careless engineering.
I wouldn’t even call this a hack, if it’s left open to the public.
Broadsoft was responsible for exposing the Time Warner Cable (TWC) data. Time Warner (TC) is an entirely separate entity (TC does NOT = TWC).
Hey thanks for that clarification Alan.
Also time Warner cable is no longer TWC . it is now spectrum.
Buckets have zero access beyond the creator. “Easiest way to grant access is to make it public”… that same statement applies to a cisco firewall in an onprem enterprise. And allow any rule is simple but terribly wrong. IAM or bucket policies are no more complex than any enterprise grade firewall. Lets not excuse the behavior of the admin due to ignorance.
Not excusing it, just saying it happens that way, same reason by MongoDB worked out of the box with no auth and listening on every interface. Not ideal, but a lot of things are done in the name of ease and speed of deployment rather than looking at it with an eye on risk and the repercussions.