SourceForge has posted info about current infrastructure and service restoration activity at http://sourceforge.net/blog/sourceforge-infrastructure-and-s...
[Disclosure: I work for SourceForge]
15 karma · joined September 9, 2014
[Disclosure: I work for SourceForge]
1. Fault with storage platform was due to a platform bug; we're working on data validation and where necessary restoring from backups 2. Operations staff worked overnight and are continuing work on service restoral. Operations staffing has been split between rapid recovery (expediting restoral) and data validation. 3. Slashdot site service was restored. 4. Work is in-progress to restore SF site, download data, mailing lists, and project web and every other service.
[Disclosure: I do work for SourceForge]
We suspended s_nakamoto's account 2 hours and 17 minutes after the attacker gained access to that account.
After generating a list of changes made, confirming method of attack, and identifying no serious changes to project content, the project was restored to its pre-attack state, and the compromised user account was removed from the project.
Risk to the community is believed to be low, as file content wasn't modified.
Regards,
Roberto Galoppini, SourceForge.net