While San Francisco residents might not be happy that they\u2019ll again have to pay fares to ride the city\u2019s rail system, the reason they again have to do so is understandable. Plus, it provides an excellent example of the importance of maintaining a backup and using complex passwords.<\/p>\n
<\/p>\n
A hacker or group of hackers, operating under the moniker Andy Saolis, managed to halt the collection of fares by the San Francisco Municipal Transportation Agency (or Muni) by hacking their station computer system and introducing a strain of ransomware into it. As a result, Muni employees were unable to access their workstations and some of the agency\u2019s systems were disabled.<\/p>\n
However, the hacker claimed to have accomplished more, as ticketing kiosks across the city would only display \u201cyou hacked. ALL data encrypted.\u201d The ransom demand for the decryption key was approximately $73,000 in Bitcoin. Despite the hacker\u2019s apparent confidence in their accomplishment, Muni elected to not pay the ransom, deciding instead to restore their systems from a backup and allowing cybersecurity experts to strike back against the hacker, not just once, but twice.<\/p>\n
Two independent vigilante hackers managed to access the email account of \u201cAndy Saolis\u201d to collect information that helped to stop the attack, both by correctly guessing the answer to the account\u2019s security question. It would seem that the hacker(s) known as Andy Saolis had been active for a while, but had never before targeted anything other than private companies, which very well may have led to their downfall.<\/p>\n
Once the attack was thwarted it came to light that seemingly no data, including that from Muni\u2019s customer payment systems, had been accessed, despite the attack affecting 25 percent of Muni\u2019s network. Saolis, unsurprisingly, gave a considerably different account online.<\/p>\n
Claiming to have stolen data from the payment kiosks, as well as 30 gigabytes of data from Muni\u2019s system on their employees, customers, and technical matters, Saolis wasn\u2019t shy about casting himself (or themselves) in the light of the vigilante against an unjust system.<\/p>\n
According to an email sent through Russian service Yandex.com, \u201cThey give Your Money and everyday Rich more! But they don\u2019t Pay for IT Security and using very old system\u2019s !\u201d<\/p>\n
Shortly after the attack ended, security experts were also able to establish that the emailer was based in Iran, and had gained access to the hacker\u2019s servers.<\/p>\n
Though Muni never had to pay a ransom for their data, this attack wasn\u2019t cheap, costing them the combined total of the free rides they granted to commuters as their systems were compromised. However, this total would certainly be less than the actual cost of the Bitcoin ransom, and so a good general rule to follow is to never give in to a hacker\u2019s possibly insincere demands.<\/p>\n
On the topic of the hacker, whose password was guessed by two separate strangers, how weak must this password have been? While nobody should ever complain about a hacker being foiled, it goes to show how a complete stranger could find their way into your accounts if you aren\u2019t being careful..<\/p>\n
This case is far from over, as the Federal Bureau of Investigation and the U.S. Department of Homeland Security are still investigating the matter, which provides proof that public systems are still unable to be fully trusted.<\/p>\n
There is a lot for SMBs to learn from this story. How confident are you in your IT security? If you feel it\u2019s time for a security audit in order to determine how protected your business is from all kinds of threats, reach out to COMPANYNAME at PHONENUMBER.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
While San Francisco residents might not be happy that they\u2019ll again have to pay fares to ride the city\u2019s rail system, the reason they again have to do so is understandable. Plus, it provides an excellent example of the importance of maintaining a backup and using complex passwords.<\/p>\n","protected":false},"author":1,"featured_media":7971,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":""},"categories":[12],"tags":[],"_links":{"self":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts\/7966"}],"collection":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/comments?post=7966"}],"version-history":[{"count":0,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/posts\/7966\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/media?parent=7966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/categories?post=7966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/staging.datcomllc.com\/index.php\/wp-json\/wp\/v2\/tags?post=7966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}