News for hackers. Stuff that matters.
Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by mmaunder on Thursday April 07, 2016 @05:13PM (#11450773)
Cite yours please.
Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by Fundlab on Thursday April 07, 2016 @05:37PM (#11450924)
Is this speculative forensics or an absolute? Does the fact that they have an outdated plugin mean the leak was siphoned by that?

Im genuinely curious

Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by mmaunder on Thursday April 07, 2016 @06:29PM (#11451210)
We're just reporting what we know at this point and what we think is likely. What we know is that their web server had access to _client data_ (the client portal). Two websites had vulnerabilities - both the WP site and the Drupal site. And it is _client data_ that was exfiltrated.

So in my opinion it's highly likely that the client data was taken via either a Drupal or WP attack vector. Even if this beach didn't happen, the client data eventually would have been stolen via one of these vectors. There are thousands of bot scripts that are exploiting revslider every day and so it's inevitable the site would have been hacked repeatedly and someone would have noticed a 2.6TB database that the web server had permission to access.

To illustrate: I've seen scripts running in real-time coming into a honeypot that run 'show databases;' and then dump everything to a .sql file in a public web directory and hit that URL to download. An attacker might have gotten a partial dump and then gone OMG and gone back for seconds... and thirds, and fourths...

Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by truthfinder007 on Thursday April 07, 2016 @07:52PM (#11451620)
I think the use of "reporting" is a stretch.. you're speculating and twisting information in your favor.

You're right, data was exfiltrated... Do we know if the portal was on the same server as the website? You seem to be making that connection, but that hasn't been illustrated.

So if you're opinion is that it was either a Drupal or WordPress attack vector, why not highlight that in your article or subsequent email? Based on your email, you imply it was WordPress but fail to make this point...

Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by mmaunder on Thursday April 07, 2016 @08:55PM (#11451878)
OK "truthfinder007" whose account was created 2 hours ago and has karma of 2. I think I've had about enough of what's going on here. Tell your boss I say hi and that he owes me a beer at the next wordcamp. ;-)

Edit: And then I looked at your comment history. Seriously? http://i.imgur.com/HBqJ8vV.png

Re:WordPress Plugin Possible Cause in Mossack Fonseca Breach by RawInfoSec on Monday April 11, 2016 @03:43PM (#11474528)
Okay Wordfence CEO.

How the hell does your product prevent SQL injection attacks on a payment processor outside of the Wordpress ecosystem??? ( http://www.theregister.co.uk/2016/04/11/hackers_pwn_mossack_... )

You guys are a joke.