It’s doable this can be a false-positive brought on by a latest replace to XProtect Remediator (the automated safety updates from Apple that you simply opt-in to). The newest was on 17/12/24, as detailed by Howard Oakley. Thought there might need been one thing else pushed within the meantime that we mere mortals do not see that has prompted the present subject, because the XProtect replace was practically a month in the past…
The additional dialogue on why this impacts Midnight Commander, and particularly only for the applying as equipped by brew may be discovered right here. I say ‘particularly’ with warning, as I’ve not seen many reference to the difficulty elsewhere, eg. MacPorts, and clearly this is a matter restricted to macOS. The MC challenge (‘upstream’) solely launch supply bundles, so elevating the difficulty with them can be fruitless.
As an interim answer it’s doable to get mc working once more by doing a build-from-source set up, after eradicating the present set up information. brew will set up any prereqs for the construct and may solely take a minute to finish. brew assumes a working Xcode CLT set up and would possibly immediate if that wants consideration beforehand.
Any outdated binaries eliminated by the macOS Malware safety could have been moved to the Bin, and may be safely deleted.
% brew uninstall mc
% brew set up --build-from-source mc
Up to date bottles – 15/01/25
The difficulty has been sorted out by rebottling, and in line with the maintainer, some motion from Apple additionally. See https://github.com/Homebrew/brew/points/19078#issuecomment-2585900449
To repair:
% brew uninstall mc
% brew replace
% brew set up mc
I’ve examined, and all Okay.