(07 May, 2022 - 11:43 AM)StarkRDP Wrote: Show MoreAs in all other similar cases, you or the person who had access to the server has been infected.
Speaking of rdp.sh no one can see your server password beside you (not even the support can) and thus there is no one other responsible for any loss than you.
Good luck on trying to sue us. The only person we can sue here is you for the public defamation.
We are a group of over 50 people doing this and only a few of us used rdp.sh, everyone else was fine who hasnt used rdp.sh
The 4 ppl including me where the only one who hosted it on rdp.sh and we are the only ones who got scammed.
Youre telling me that we got "infected" but there wasnt anything by what we could be got infected, because there was nothing else installed.
The only one singe tool ive downloaded to this rdp was one was which I combiled myself from the sourcecode.
Of course I was searching the mistake on my end first, but when I compare everything togheter there is just nothing left, also why the "hacker" was cleaning the logs when they got the money already.
Youre right there is no way now to proove to the audience what really happened and you guys will telling the same shit over and over again.
Hopefully this thread will help some people to make the right decission when choosing a rdp provider.