New day, new HBO hack. This time, a few of the channel’s Twitter accounts were broken into by the OurMine hacking group. The group targeted the main HBO twitter account but were also able to hack into the dedicated Twitter accounts of two of the network’s biggest shows: Game of Thrones and Girls.

Once inside, the hackers tweeted the same phrase on all accounts: “Hi, OurMine are here, we are just testing your security, HBO team please contact us to upgrade the security.” They also tried to get #HBOHacked trending.

The rogue tweets lived for only an hour after HBO regained control of its accounts. HBO is now “investigating” the hack, says The Guardian.

This new OurMine social media hack is yet another bump in the road after a tough few weeks for HBO. Back in July, 1.5 TB worth of sensitive data was hacked. The hacker responsible for this first attack calls himself Mr. Smith, and has demanded $6 million to give back the data; just last week, it came out that HBO had offered Mr. Smith $250,000 before he went public with his information, which is obviously well short of what he is asking for.

The Mr. Smith hack has been a trove of information. So far, he has leaked: personal phone numbers of Game of Thrones actors, episodes of Game of Thrones, Curb Your Enthusiasm, Insecure, Ballers, and the movie Barry. The hacker has also released files on the second season of Westworld and the seventh season of Game of Thrones.

"It has been widely reported that there was a cyber incident at HBO," an HBO spokesperson told Variety in response to the Mr. Smith hacks. "The hacker may continue to drop bits and pieces of stolen information in an attempt to generate media attention. That's a game we’re not going to participate in."

Additionally, four men were arrested in Mumbai, India in connection to leaking Game of Thrones episode "The Spoils of War" ahead of its original Aug. 6 air date. 

And to top it all off, just yesterday, episode 6 of Game of Thrones was leaked days before its official broadcast on Sunday. HBO said a third-party vendor was at fault for this leak, which seems like an unfortunate unforced error at this point.

Also Watch