6 years
x
194 Views

Mysterious malware infects 30,000 Mac computers

by Lance Whitney in Security on February 22, 2021, 7:37 AM PST

Known as Silver Sparrow, the malware’s intent is still unknown as it has yet to deliver an actual payload, says security firm Red Canary.
malware in a computer system

Image: kaptnali, Getty Images/iStockphoto

A piece of malware that has infected almost 30,000 Mac computers has triggered questions over its intent and ultimate payload.

SEE: Security Awareness and Training policy (TechRepublic Premium)
More about cybersecurity

10 fastest-growing cybersecurity skills to learn in 2021
Meet the hackers who earn millions for saving the web
Top 5 programming languages for security admins to learn
End user data backup policy (TechRepublic Premium)

Based on data from Malwarebytes, the malware dubbed Silver Sparrow by researchers at Red Canary, has so far landed on 29,139 macOS machines across 153 countries, including the US, UK, Canada, France and Germany. Questions have arisen because the malware hasn’t actually done anything malicious yet, meaning there’s been no observed payload delivery and no conclusions as to its purpose.

What is known is that Silver Sparrow is a strain of malware designed for Macs powered by the new Apple M1 chip, which the company introduced late last year as a move away from Intel architecture. This makes it only the second known piece of macOS malware to target the new chips, according to Ars Technica. With the missing payload piece and other questions, the malware has led to concerns among Red Canary researchers.

“Though we haven’t observed Silver Sparrow delivering additional malicious payloads yet, its forward-looking M1 chip compatibility, global reach, relatively high infection rate, and operational maturity suggest Silver Sparrow is a reasonably serious threat, uniquely positioned to deliver a potentially impactful payload at a moment’s notice,” Red Canary said in a blog post published last Thursday.

For its analysis, Red Canary said that its researchers uncovered two version of the malware: One compiled for Intel x86_64 architecture only and a second compiled for both Intel x86_64 and M1 ARM64 architecture. So far, the binary code for Silver Sparrow doesn’t seem to do much, prompting Red Canary to refer to it as “bystander binaries.”

The malware is distributed in two different packages—updater.pkg and update.pkg. Both use the same techniques for execution, with the only difference being in the compilation of the binary code. The binary for updater.pkg seems to be a placeholder for other content. For now, executing the script simply displays the message: “Hello, World!” Similarly, executing the binary for update.pkg displays the message: “You did it!”

The malware infects a machine through a specific process, Tony Lambert, intelligence analyst for Red Canary, explained to TechRepublic:

While performing routine tasks on the internet, such as viewing search engine results, you encounter a page that tells you to download an update. Once downloaded, you click through any warnings and install the downloaded PKG file. During installation, the malware creates a persistence mechanism, which ensures that it remains on the machine. After that, scripts run at regular intervals to check for any additional payload.

One unique aspect of Silver Sparrow is that its installer packages take advantage of the macOS Installer JavaScript API to run suspicious commands, according to Red Canary researchers, the first time they’ve seen this tactic used by malware.

“The novelty from this threat is twofold,” Lambert said. “First, we don’t commonly see malware using JavaScript inside a PKG file to perform actions like Silver Sparrow does. Second, one version of Silver Sparrow contained a placeholder executable compiled to support M1 architecture.”

Silver Sparrow is a potential threat because it allows arbitrary code to be downloaded and executed without the user’s knowledge, Lambert added. This can include potential code from any URL. Though Silver Sparrow seems benign for now, the people behind it could simply be laying the foundation for a malicious attack.

“The ultimate goal of this malware is a mystery,” Red Canary said in its blog post. “We have no way of knowing with certainty what payload would be distributed by the malware, if a payload has already been delivered and removed, or if the adversary has a future timeline for distribution. Based on data shared with us by Malwarebytes, the nearly 30,000 affected hosts have not downloaded what would be the next or final payload.”

Malwarebytes itself doesn’t seem to be as concerned about Silver Sparrow.

“Most of what was found wasn’t really operational,” Thomas Reed, Malwarebytes director of Mac and Malware, told TechRepublic. “There are signs that this may be a discontinued campaign, as the command & control servers were not providing a payload at the time of discovery, and the data we’ve seen indicates that most of the ‘infected’ machines actually had the malware self-destruct at some point and are no longer truly infected.”

Reed said he doesn’t see this as a potential threat as no truly active infections seem to be in the wild and the malware doesn’t appear to still be active in its present state. But he acknowledged that the appearance of a yet-to-be-discovered variant of this malware could pose a threat. As such, people should remove all the components of the malware from their computer, something a program like Malwarebytes can do for free.

Aware of Silver Sparrow, Apple has taken steps to mitigate it as well, a company spokesperson told TechRepublic. After discovering the malware, Apple revoked the certificates of the developer accounts that signed the packages, which prevents new computers from getting infected. Further, the company employs such protection as the Apple notary service to detect and prevent malware from running on a machine.

Even with Apple’s protection, Red Canary advises users to run third-party antivirus or antimalware products to supplement the antimalware protections in the operating system. On a more technical security or developer level, Red Canary also offers the following advice to enterprises:

Look for a process that appears to be PlistBuddy executing in conjunction with a command line containing the following: LaunchAgents and RunAtLoad and true. This analytic helps find multiple macOS malware families establishing LaunchAgent persistence.
Look for a process that appears to be sqlite3 executing in conjunction with a command line that contains LSQuarantine. This analytic helps find multiple macOS malware families manipulating or searching metadata for downloaded files.
Look for a process that appears to be curl executing in conjunction with a command line that contains s3.amazonaws.***. This analytic helps find multiple macOS malware families using S3 buckets for distribution.

Editor’s note: This article has been updated with additional comment.
Tech Republic

New Confession

Mr John…she stammered.shhhhh I said. If I tell your mom you were actually f****** on my couch she’ll beat you ground you or? Yeah I know. How can we make this right? Well if I won’t tell you can’t tell. Come over here and sit on my lap. No straddle my legs and face me. Are we going to really f***? No sweetie. You are 13, and I’m not insane. But a little foreplay to give you your o***** would be a nice way to end your night. She edged up to me , saw the huge bulge in my pants. And spread her thighs apart and nestled her tight little a** on my legs. God she was warm. I parted her blouse snd palm ribbed her n******. A minute later she closed her eyes and leaned backwards, her tongue lolling in her mouth. I Slowely began sucking and licking her now hardening n******. Slurp. Slurp. I suckled her tips. Oh oh Mr John you really know how to s*** n******. She panted. Now I ran my fingernails from her spread open knees to her very inner thighs. She felt terrific and parted her thighs wider. I smelled her young eager p**** aroma. It was intoxicating. You smell so fresh sweetie. My name is Lizzie. Call me Lizzie. As I messaged her thighs she respread hrr thighs. Am I all drippy? She asked. I moved my fingers to the edge of her vaginal flesh. Yes swee Lizz you are a little slippery. Met I touch your very soft p**** Lizz? Yes yes I ran my fingers over the slushy slit. From a** hole to her c*** I let my fingers fiddle and wiggle in between her inner and outer lips. Nearly virgin as she was the flesh was delicate and lovely. My fingers and c*** tingled as I played with her p****. She gasped a little. Oh oh oh press on my c******* Mr John. Rub it gently. It’s all on fire down there.what’s on fire? My hot p**** Mr John. I know Lizz but it will get much much hotter . I felt up between her inner lips and gently rubbing her buttonwatcher her face contorted as she bit met bottom lip. Ooooo ooooo. Ooooo she slobbered. Yes honey let it go let it grow wild up into your belly and spread. I will get much more exciting. Her 13 yr old p**** enraged my c*** snd it twitched maddeningly. I caressed the wet button slowly and drew circles around it then tapped it seversl times. Then pinched it and then pressed on it. Then gripped the tiny button. Oh oh oh I’m i’m ( I stopped all movements. She unstiffenefd her torso and nearly collapsed. No no no don’t stop. Just for a minute. Your climb up will be even better. Oh s*** oh s*** I have to peepee. Go ahead let it come. She let loose snd peed into a cup i ok held. I watched her urinate and nearly blew my wad. She finished. I wiped her puss and slid my finger to her wet c******* again. Yes yes yes as I rolled my finger over the now very tender c*** I lifted her Fanny closer to my chest. Now my hot breath covered her c***. But also bared her tiny button slowly and hole. It was pink and puckered. Tho delicious looking I chose to use my other finger to eiggle it over her sss hole. She jiggled her a** cheeks trying to tighten them, but I pulled them apart and slid my index finger up into her lovely little yielding hole as fsr as I could. Once fullly inserted I wiggled it round and round and round. She gagged a bit but I gently lifted the hood on her c*** and sucked it into my lips. My waiting tongue began licking her c*** faster and faster. She grunted. She cried out as her wave of lust built up. As I sucked harder she waved her arms skyward snd grabbed her n******, pinching hard. A wild scream may have begun, but no sound was emitting from her gasping mouth. Her a** rippled and bounced on my legs. She stiffened and then looking into my eyes she collapsed against my body. Gasping for oxygen she sagged into e***** exstacy. Oh god oh god. I hugged her tiny body warmly. Was it good for you Lizz? I asked.

Related Confessions