5 ms·
More likely this was done via a signature update to xprotect, which is essentially a background antivirus process in macOS.
by msbarnett 7y ago
More likely this was done via a signature update to xprotect, which is essentially a background antivirus process in macOS.
- snuxoll 7y agoDoesn't appear so, current XProtect version remains at 2103 which was released a couple months ago now.
- saagarjha 7y agoThe update from today updates the MRT configuration data.
- msbarnett 7y agoI haven’t checked, but are you looking at the version of the binary itself, or the MRT signature files it uses
- snuxoll 7y agoChecked XProtect.meta.plist inside the app bundle, forcing an update check with softwareupdate has no impact either. Perhaps it’s a staged rollout, but at least on my iMac there’s no sign of updated signatures.
- msbarnett 7y agoYeah you’re just looking at the version of the xprotect binary, not the malware signature data files, which don’t live in the bundle and get updated more regularly. They also ship silently via system_installd, you’re not going to see anything in the software update GUI
- snuxoll 7y agoThe signature files also live inside the XProtect.app bundle, unless in true Apple fashion they’ve got other stuff that’s lurking elsewhere in /System that I can’t locate.
- ReverseCold 7y agoSince the update is called "MRTConfigData" - and that has to do with XProtect according to https://discussions.apple.com/thread/250079600 https://discussions.apple.com/thread/250079600 - you're probably right.