RE: Security Breach 12-31-2014, 11:39 AM
#21
Seems like we aren't the only site this happened to. 
It wasn't through the hosting company. I considered it a possibility early on, but nope.
But, nobody is getting into the ACP ever again. It's really well hidden.
"dongs.php" - literally the only reason I didn't get mad about the whole thing. To be honest, we've done worse to others. @phyrrus9 and a couple others believe that no data was taken, although I am slightly inclined to believe otherwise. That being said, they have seen everything that I have, and that's their conclusion. Either way, everyone should be careful about their passwords.

(12-30-2014, 11:13 PM)Ominous Wrote: Could it have been possible that Sinisterly was breached through your hosting provider? I previously had my forum hacked because of poor security on the host I was on.
Otherwise, it might be a vulnerability in a plugin that is in use, or even in MyBB itself, since the team isn't working on 1.6 anymore, unfortunately.
Someone has the right idea. If you're able to find a critical exploit in 1.6.16 now, practically every other MyBB forum is at your mercy since 1.6 isn't going to be updated, and people are too lazy to switch to 1.8 because themes and many plugins will be incompatible.
It wasn't through the hosting company. I considered it a possibility early on, but nope.
(12-31-2014, 01:36 AM)phyrrus9 Wrote: A backup from 12/26 was restored, so anything made after that is now nonexistent. It does not look as though any breach was done via the hosting company as the injection vector was identified to be the ACP. How they got in there, we don't yet know.
But, nobody is getting into the ACP ever again. It's really well hidden.
Spoiler:
"/reallywellhidden" was the old admin panel link. Creative, right?
(12-31-2014, 02:47 AM)phyrrus9 Wrote: That was @Oni who came to that solution, they planted a remote shell from there. We intercepted it before anything serious was done (the filename was hilarious), and then took the remainder of the 2 days to implement countermeasures and do damage control.
"dongs.php" - literally the only reason I didn't get mad about the whole thing. To be honest, we've done worse to others. @phyrrus9 and a couple others believe that no data was taken, although I am slightly inclined to believe otherwise. That being said, they have seen everything that I have, and that's their conclusion. Either way, everyone should be careful about their passwords.










![[Image: 7ajmN5P.jpg]](https://i.imgur.com/7ajmN5P.jpg)
![[+]](https://sinister.ly/images/modern/collapse_collapsed.png)












![[Image: dHJ4Beo.gif]](http://i.imgur.com/dHJ4Beo.gif)












