This is the question that most of the steam users are wondering in the last hour. But the real question, is WHO made it? Are hackers behind this?
Well, you went to the right place at the right moment, because our reporter already "interview" a steam worker a couple of minutes ago and that's what we got:
Do you know about what's just happening with your servers?
- Well, we are working on it since the first report we got and we were about to solve it in a few minutes.
- We actually don't know, we were planning on solve it really soon but the problem is servers didn't respond at all in the first half of hour.
- Surely yes! We wouldn't be the leaders on games digital distribution if we wouldn't of care of our users.
- Yes, and that's one of the worst problems at the moment. Anyway we will shut down our servers as soon as possible.
UPDATE 2015/12/26
Seems that, who made the steam servers go down for more than one hour, was the hacker group "SkidNP", who already mentioned their intentions to start a group hack against Minecraft and Steam servers on 2015/12/25.
This means, it's higly reccomended to change your Steam password and, if you transferred money using PayPal system, change your PayPal account password.
UPDATE 2015/12/26
Steam is still partially down. We can say it due to the fact that some servers of Steam are still not operative, all of them mainly store data for the steam community website.
This morning, we questioned to a steam worker: "when will the steam community website be back online?" and this was the answer:
- The servers are now working fine, without any problem. But we are still working to know what was the cause of the malfunction and we are doing checks to be sure to not to encounter this problem again.
UPDATE 2015/12/30
As we already specified, it could of had been a group hack to the Steam servers. It was, in fact, a DoS attack. Still, none of the Steam workers know who the hacker group was, it probably could of had been the hacker group "SkidNP", who already announced they wanted to send a hacker attack to the Steam servers.
After 5 days, finally the Steam team wrote down the report about what happened on 25th of December into their servers, this is the article:
We'd like to follow up with more information regarding Steam's troubled Christmas.
What happened
On December 25th, a configuration error resulted in some users seeing Steam Store pages generated for other users. Between 11:50 PST and 13:20 PST store page requests for about 34k users, which contained sensitive personal information, may have been returned and seen by other users.
The content of these requests varied by page, but some pages included a Steam user’s billing address, the last four digits of their Steam Guard phone number, their purchase history, the last two digits of their credit card number, and/or their email address. These cached requests did not include full credit card numbers, user passwords, or enough data to allow logging in as or completing a transaction as another user.
If you did not browse a Steam Store page with your personal information (such as your account page or a checkout page) in this time frame, that information could not have been shown to another user.
Valve is currently working with our web caching partner to identify users whose information was served to other users, and will be contacting those affected once they have been identified. As no unauthorized actions were allowed on accounts beyond the viewing of cached page information, no additional action is required by users.
How it happened
Early Christmas morning (Pacific Standard Time), the Steam Store was the target of a DoS attack which prevented the serving of store pages to users. Attacks against the Steam Store, and Steam in general, are a regular occurrence that Valve handles both directly and with the help of partner companies, and typically do not impact Steam users. During the Christmas attack, traffic to the Steam store increased 2000% over the average traffic during the Steam Sale.
In response to this specific attack, caching rules managed by a Steam web caching partner were deployed in order to both minimize the impact on Steam Store servers and continue to route legitimate user traffic. During the second wave of this attack, a second caching configuration was deployed that incorrectly cached web traffic for authenticated users. This configuration error resulted in some users seeing Steam Store responses which were generated for other users. Incorrect Store responses varied from users seeing the front page of the Store displayed in the wrong language, to seeing the account page of another user.
Once this error was identified, the Steam Store was shut down and a new caching configuration was deployed. The Steam Store remained down until we had reviewed all caching configurations, and we received confirmation that the latest configurations had been deployed to all partner servers and that all cached data on edge servers had been purged.
We will continue to work with our web caching partner to identify affected users and to improve the process used to set caching rules going forward. We apologize to everyone whose personal information was exposed by this error, and for interruption of Steam Store service.
-Valve 11:00
updates in real time.

Nessun commento:
Posta un commento