Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

hassiman

macrumors regular
Original poster
Aug 30, 2006
120
11
San Diego
How do I fix it❓
 

Attachments

  • 7BB9F689-508E-4EF4-ACE9-7B03C857ABE1.jpeg
    7BB9F689-508E-4EF4-ACE9-7B03C857ABE1.jpeg
    986.5 KB · Views: 98
How do I fix it❓
The real question is "what is the it". The error is a symptom of something (a script of some sort probably) asking to do a command with sudo. So need to track down the cause.

Questions:
1) What were you doing immediately before the error?
2) What scripts do you have which might be doing an sudo?
3) Do knockknock and Malwarebytes https://www.malwarebytes.com show anything bad?
 
The real question is "what is the it". The error is a symptom of something (a script of some sort probably) asking to do a command with sudo. So need to track down the cause.

Questions:
1) What were you doing immediately before the error?
2) What scripts do you have which might be doing an sudo?
3) Do knockknock and Malwarebytes https://www.malwarebytes.com show anything bad?
On Boot....

I will look at startup apps.

Any recs on good antivirus programs for Macs? Is Malware Bytes effective? Not used Knock Knock...
 
On Boot....

I will look at startup apps.
You need to look at ALL the areas which can start processes - not just "Login Items" in system Preferences. In particular all the items in ~/Library/LaunchAgents, /Library/LaunchAgents, and /Library/LaunchDaemons.

Malwarebytes is good at scanning such locations for malware. Just scan with the free version.

Note: Your problem could be due to something in a legitimate app you use but which has now run foul of tighter restrictions in macOS 12. Are you running latest versions of all your apps?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.