Hah! My curmudgeonness is vindicated! I still use bash, so the .zshrc trick won't work, and I refuse to use Launchpad, instead just using an alias to the Applications folder, so I'd never see the second one.One new method creates a file named ~/.zshrc_aliases that contains the malicious payload. The new variant then appends a command in the ~/.zshrc file to ensure that the created file is launched every time a new shell session is initiated. The other new method creates a fake Launchpad app and replaces the legitimate Launchpad path entry with the path for the new one.
"Microsoft Defender for Endpoint on Mac now detects the new XCSSET variant..."Well, I don't believe Microsoft makes a malware detector for macOS? So in this situation, I think they're in it for the street cred.
Hah! My curmudgeonness is vindicated! I still use bash, so the .zshrc trick won't work, and I refuse to use Launchpad, instead just using an alias to the Applications folder, so I'd never see the second one.
I eventually moved to bash from tcsh because it was too lonely over there. I'd happily move back though, if there's more than just the two of us!I see your curmudgeonness and raise you. tcsh for the win!
I've often maintained that one thing pushing society to its breaking point is the fact that the world has become too complex for any reasonable human being to even hope to truly understand.
Why did we end up with the truly stupid version of Dogbert? Because we are so dumb there was no need to upgrade to a marginally less drivel version?
Wow... a whole bunch of irony lurking in that cartoon.
No. .zshrc_aliases is just another file, it has no special meaning to zsh, it's just a file with an innocuous name that someone might expect to be sourced from .zshrc. It could just as well be sourced from .bashrc, or called .bashrc_aliases.Does this mean reverting to use bash as default over zshell is safer?
For this particular attack, that seems to be the case, but not because there‘s anything inherently superior about bash. The perps could have trivially victimized bash users by similarly modifying ~/.bashrc after breaking in; they just didn’t bother.Does this mean reverting to use bash as default over zshell is safer?
And the real irony is that Scott Adams turned turned out to be just as gullible.Wow... a whole bunch of irony lurking in that cartoon
The referenced post in the article states some of the binaries associated with this malware are signed, so it’s only a matter of time before Apple revokes and blocks and XProtect does its job - though there’s always a higher risk on dev systems that some macOS security protections might be disabled.A scenario where XProtect should protect, right?
Any news from Apple on this?
Ooh! Ooh! Do the "Macs don't get viruses" bit next!The irony of Microsoft, purveyors of all that is hole-y, pointing this out?
“Physician, heal thyself.”
The first paragraph makes it clear that the malware targets app developers. In other words, if you aren’t an app developer on macOS, you could have stopped reading the “mumbo-jumbo” right there. If you are an app developer and don’t know what a zero-day is…well, this would be a good time to start doing some outside reading.WHO, exactly, is this article for? I mean, all this tech mumbo-jumbo is impressive but I'm not a techie or coder. I don't even know what a "zero-day" is (and is not explained).
Eeep! Eeep! Do the "Do the Macs don't get viruses bit" < bananas > < feces > < neckbeard > bits next.Ooh! Ooh! Do the "Macs don't get viruses" bit next!
I see what you did there.Eeep! Eeep! ...