Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

How do I handle suspected malware in macOS and protect my MacBook Pro?

Its just couple of days since I started setting up my new MacBook Pro, and see what I found:

A file ~/Library/LaunchAgents/com.ntpebadwvugmokrc.plist was created automatically and is running now.

also found ~/.passphrase, a hidden file associated with this campaign. The documented malware uses it to hold the Mac login password after showing a fake system prompt. I did not open the file, so I cannot confirm what it contains or prove what was transmitted. Treat your Mac password—and accounts accessible from this Mac—as potentially compromised.


It is set to stay running, hides an AppleScript inside base64, and launches a command that contacts an external site and pipes the response to osascript. That is strong evidence of unauthorized remote-code execution behavior—not a normal Mac item. I cannot determine from this inspection what the remote code did or whether data was taken.


I have collected the evidence and resetting my Macbook as temporary solution.


Does any one else has similar experience?


In plain language, it does this:


  1. Starts at login and tries to stay running. The file has RunAtLoad and KeepAlive enabled. It was still running when I checked at 2:04 PM today.
  2. Hides its instructions. It takes a long encoded string, decodes it, and runs it as an AppleScript.
  3. Looks up where to connect. The AppleScript asks several Polygon blockchain servers for a value that it decodes into a server address. This is a way to change its destination without editing the file;
  4. Downloads and runs more instructions. It sends an identifier to that server and pipes the server’s response directly into osascript. In effect, whoever controls that response can supply code for the Mac to run.
  5. Important distinction: this file shows the loader—how it fetches and runs further code. It does not contain the full code returned by the server, so the file alone cannot tell us exactly what was accessed or whether anything was stolen. The separate .passphrase file we found remains a serious concern, but I dont understand its contents.


[Re-Titled by Moderator]

Original Title: suspected malware in macOS


6 replies

macOS is very robust against malware, with multiple layers of passive and active protection.


Protecting against malware in macOS - Apple Support


However, what macOS cannot fully protect against is a foolish decision by the user. If you paste unknown text into Terminal and execute it despite the warnings from macOS (and the new copy/paste block from browsers to Terminal), if you install unsigned software and run it despite the warnings, etc., then you can enable malware to run on your Mac.


If that has happened, your best course of action is to wipe your Mac and start from scratch (not from a backup made post-infection!).


Erase your Mac and reset it to factory settings - Apple Support


It's unclear what your goal is here. If your intent is to report something to Apple, be aware that “we” are users like you and have no power to implement any suggestions. Apple employees are generally precluded from even reading these forums, with the exception of moderators who only monitor for compliance with the T&C.


If you want to make Apple aware of a security issue, go here:

Report a security or privacy vulnerability - Apple Support



Try downloading & running Malwarebytes, as it may be able to remove the associated malware.


You can install & manually run Malwarebytes for free. The paid version unlocks automatic & realtime scans.

Ah, didn't notice the base64 part (I really shouldn't be posting while fighting a cold).


But, as I think I understand it, this isn't something that can be fixed by simply removing LauchAgents and LaunchDaemons. A complete wipe of the Mac may be necessary.

As etresoft noted, these infections are caused by the user. You (or someone else who uses that Mac) downloaded and installed it. Usually unknowingly, but you still did it to yourself.


See this topic by John Galt.


About those "<app> will damage your… - Apple Community


What you post here should be in List mode. Make sure the window listing is wide enough to see the entire file names. Such as this:



From the lists you post, we can highlight which ones to remove while in Safe Mode.

hid272 wrote:
Does any one else has similar experience?

Certainly. But over the past few years, it's become common knowledge that these malware infections primarily come from running pirate apps downloaded via torrent, or downloading hacking tools in order to bypass some copyright restrictions, to watch a paid video stream or sporting event, perhaps.


hid272 wrote:
It is set to stay running, hides an AppleScript inside base64, and launches a command that contacts an external site and pipes the response to osascript.
That is strong evidence of unauthorized remote-code execution behavior—not a normal Mac item. I cannot determine from this inspection what the remote code did or whether data was taken.
[Re-Titled by Moderator]
Original Title: suspected malware in macOS


"base64" stands out here and something you clicked on an ran...


These exploits are well document— Some examples: ClickFix, Shamos infostealer, Cloudflare

Visual template to be used, such as Google Meet, Google CAPTCHA, Cloudflare


trick users into thinking that the verification step is legitimate


some CASE IN POINT— ASC


Understanding and reversing a suspicious terminal command

ref: Understanding and reversing a suspicious … - Apple Community


ref: Terminal scam! Advice needed please.

Terminal scam! Advice needed please. - Apple Community


ref: Mac security concerns after suspicious Terminal command

Mac security concerns after suspicious Te… - Apple Community