AO3 returns after security incident; data breach not ruled out
Part of the AO3 story · since 15 Nov
- Sun 15 Nov, 16:56 UTC. cybersixt, first report. AO3 returns after security incident; data breach not ruled out. This article, 1st of 1.
Archive of Our Own (AO3), the fan fiction archive run by the non-profit Organization for Transformative Works (OTW), came back online on 15 November after 17 days offline following a security incident, but with several features switched off. OTW says it still has no reason to believe the user database was taken, and still cannot rule it out, according to its status page.
The site went down at 07:13 UTC on 29 October, at first described as maintenance. At 01:27 UTC on 30 October OTW said it had detected "evidence of a security incident" earlier that day, that it was still working out the scope, and that the site would stay down for at least two and up to four weeks. It posted the same warning on X.
What may have been exposed
OTW said the AO3 database holds account information that may include each user's username, email address, IP address and a hashed version of their password. It said passwords are stored with industry-standard hashing, but that no hashing method fully protects a weak or reused password from being cracked. AO3 does not collect real names, and OTW said donor information is kept in a separate system that is never linked to AO3 and was not exposed. It said no works, bookmarks or other AO3 data had been deleted.
What changed on return
In its 15 November update, OTW said it brought the site back before the four-week mark by temporarily disabling some features: user and collection icons are not displayed, importing works from other sites is unavailable, and works can only be downloaded as HTML. It said those features will return and that no icons were deleted. A traffic queue may delay page loads. OTW has hired a security firm to review the incident and the site, but said it will not describe the changes it has made while this is a security matter.
OTW paused the automatic deletion of drafts during the outage and will keep it paused until 29 November so users can save or publish them. On 6 November it said that some notification emails queued before the shutdown had been sent out during the restore work and were genuine. The Associated Press also reported the limited return.
What AO3 users should do
OTW recommends that users change their AO3 password, make sure the email address on their account is current, and change the password on any other site where they used the same one. Because email addresses may be among the exposed data, users should be wary of messages that claim to come from AO3 and ask them to log in or confirm their account.
What is not known
OTW has not said how the attacker got in, what the attacker was able to reach, why the disabled features were chosen, or whether it will notify users individually if the review finds the database was accessed.
How the story developed
1 article from 1 outlet since 15 Nov. Quiet since 15 Nov. This was the first report.
- Sun 15 Nov, 16:56 UTC. cybersixt, first report. AO3 returns after security incident; data breach not ruled out. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Sun 15 NovDay 01
- AO3 returns after security incident; data breach not ruled out16:56 · cybersixt · First report · This article, 1st of 1
Sources
More reporting
- Suspected Optimizely breach planted card stealer on 186 websites16 Nov
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS