Yet More PS5 Security Concerns as Another High-Profile Account Is Hacked | #hacking | #cybersecurity | #infosec | #comptia | #pentest | #hacker


Image: Push Square

Earlier this year there was a big hullabaloo about a social engineering scam, impacting dozens upon dozens of PlayStation players.

The story hit the news in a big way when longtime podcaster Colin Moriarty had his account boosted, leading to widespread panic in the community.

While the Sacred Symbols host was able to use his connections to regain access to his profile, the story is not over by a longshot.

Overnight, prominent fan RealRadec – a positive voice in the community, with more than 30k followers on X – revealed that he was the latest victim of Sony’s shoddy security.

For those who missed the previous news – and it’s really important – it’s been discovered that accounts can be hijacked using just a few potentially public details:

  • A PSN username
  • An associated email address
  • A transaction ID or purchase date

Some of this information can be easily obtained online, while others can be inferred.

It’s real scary stuff, and the hope was that PlayStation would have tightened things up after what happened to Moriarty.

The reality, as we move towards an all-digital future, is that PSN accounts can be attached to potentially thousands of dollars in game purchases, not to mention countless gaming memories and achievements, through Trophies et al.

This may not have been a particularly big deal in the early PS3 days, when Trophies were still new and digital purchases were much less common. But in an age where PlayStation is desperate to do away with physical media, it’s terrifying.

I must admit, I’d expected PlayStation to have resolved these issues after the public situation with Moriarty earlier in the year.

The fact that this is still happening to prominent members of the fanbase beggars belief, and it’s understandably got the entire community on edge once again.

This simply cannot keep happening.





Click Here For The Original Source.

——————————————————–

..........

.

.