🤔
🤷‍♂️

😂

🤷‍♂️

🤷‍♂️

😂

🤷‍♂️

🤷‍♂️

🤷‍♂️

😂

🤷‍♂️

If only I could understand why they still not fixed this problem (same problem from at least long months ago now) or if somehow they could not fix it, why not add some error message instead of allowing the posts to be published with this problem...
🤷‍♂️

Ahh, thanks for the reply, deleted the post.
I'm just coming here randomly time to time, to tweet some random images... but looks like this site is still not stable enough even for doing that.
🤷‍♂️

😂

🤷‍♂️

😂

How many people's machines could got infected in this way who never learned about the malware infection, or if did, only later, and never finding out that the infection happened "thanks to the help" of Microsoft?
🤔
🤷‍♂️
(2/2)

Anyway, at least Any_Process got some luck in his misfortune, as in his case, the "Microsoft tech support" person infected his machine at the "right time" - when the C2 panel of the malware got pwned & that notification added...
(1/2)

"It's literally easier to crack windows than to pay for it"
Looks these days, it's not only easier, but if you're cracking yourself properly (or ask someone you know who can do it properly, so safely), it's safer too...
😂
🤷‍♂️

For the "such things happened before" part, just found this
@bleepingcomputer.com article from 2023: www.bleepingcomputer.com/news/securit...
🤷‍♂️

😂
🤦‍♂️
🤷‍♂️

Microsoft's support unintentionally infects people's machines with malware?
🤔

It's that time of the year again...

😂

😂
🤷‍♂️

🤷‍♂️

2025-01-08 (Wednesday): Alright, man! I could use a vacation! The final #phishing page at faernleys[.]com didn't work for me, though.