Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
exploitHackVulnerability

PamStealer macOS Malware Adds Live C2 Decryption

By ogwatermelon
September 26, 2026 5 Min Read
0
September 25, 2026

Cybersecurity researchers at Jamf Threat Labs have identified a major evolution in the PamStealer macOS infostealer family. The new variant, distributed through a fake cryptocurrency wallet called Wavel, adds server-side payload decryption and four redundant persistence mechanisms. It also marks a shift from Rust to Swift in the stealer’s second stage. This evolution reflects a deliberate investment in delivery infrastructure designed to evade static analysis and maintain long-term access to compromised systems.

What Happened: PamStealer Wavel Variant Adds Live C2 Decryption Chain

The third known variant of PamStealer was first observed in September 2026. Victims are lured to a convincing fake website impersonating a multichain cryptocurrency wallet named Wavel. When they click Download for macOS, they receive a disk image containing a compiled AppleScript file that triggers a multi-stage infection chain.

Jamf Threat Labs published their findings on September 22, 2026. The research reveals that this version differs from earlier Maccy, Scoppr, and Nancy variants in a critical way. Previous versions embedded decryption keys directly in the dropper. Consequently, security researchers could extract and analyze the payload offline. The new Wavel variant delegates decryption to a purpose-built utility named pkgunpack. This utility performs a live X25519 key exchange with the command-and-control server. Without active C2 cooperation, the payload cannot be decrypted or recovered statically.

Furthermore, the second-stage stealer has been rewritten in Swift. Earlier variants used Rust. The change in programming language does not alter the malware’s objectives. However, it may help the authors evade signature-based detection tools that were trained on Rust artifacts.

Technical Details of the PamStealer Wavel Attack Chain

The infection unfolds in two primary stages. First, a compiled JavaScript for Automation dropper acts as a carrier. Second, a Swift-based infostealer harvests credentials and system data.

Stage 1: The zsh Dropper and Server-Side Decryption

The compiled JXA file contains a single large base64 string. When Script Editor executes it, the string decodes into a zsh script. That script is piped into /bin/zsh -s and runs in the background. The JXA process exits immediately. This severance makes the origin of subsequent processes harder to trace.

The zsh script performs the following actions:

  • Downloads the pkgunpack decryption utility from wavel.apple03cloudstore[.]com
  • Strips the quarantine attribute and applies an ad-hoc code signature
  • Generates a fresh ephemeral X25519 keypair via pkgunpack genkey
  • Posts the ephemeral public key to the C2 server and receives an encrypted Data Encryption Key
  • Decrypts and stages the payload bundle
  • Suppresses macOS background-item notifications
  • Installs four redundant persistence methods

Because a new ephemeral keypair is generated on every execution, captured network traffic cannot be replayed to decrypt the payload. This design significantly hinders static analysis and forces incident responders to observe live C2 sessions.

Multi-Layer Persistence Mechanisms

After installing the payload, the dropper establishes four separate persistence layers. Each carries a # sysnotif-repair marker so the dropper can detect whether a layer is already in place.

  1. LaunchAgent — Registers com.apple.finder.agent via launchctl bootstrap. It masquerades as a system component and restarts every 15 seconds.
  2. Repair Script — A standalone zsh script at ~/Library/Application Support/System/.repair-run restores the payload and LaunchAgent from a local backup if either is missing.
  3. Shell Hook — Appends a block to ~/.zshrc that triggers the repair script on every new interactive zsh session.
  4. Global Git Hooks — Copies the repair script into post-checkout and pre-commit hooks. Any git operation on the system silently reactivates the malware.

Stage 2: Swift-Based Infostealer with PAM Validation

The second stage is a FAT Mach-O binary supporting both arm64 and x86_64. It is written in Swift and internally named MacClient. Four key functions are exported:

  • _MacClient_main — entry point
  • _pam_verify_login — PAM-based credential validation
  • _kc_grab_storage_item — keychain retrieval
  • _sqlite_backup_database — browser database backup

The binary presents a fake macOS wants to make changes authentication dialog. The entered password is validated through the macOS Pluggable Authentication Modules interface using login as the service name. After validation, a second fake dialog appears, mimicking a damaged-application error.

The stealer targets seventeen browsers. Standard Chromium and Firefox families are covered. However, the inclusion of Arc, Zen, Waterfox, LibreWolf, Yandex Browser, and Cốc Cốc extends the target list well beyond typical commodity stealers. The malware also harvests keychain items, system metadata, shell histories, and even the user’s profile photo via dscl.

Business and Operational Impact

Organizations running macOS face elevated risk from this variant. The server-side decryption chain makes traditional static analysis and sandbox detonation less effective. Consequently, security teams must rely on behavioral detection and network monitoring to identify infections.

  • Credential Exposure: Passwords, browser sessions, and keychain data are exfiltrated. This enables lateral movement and follow-on attacks.
  • Developer Risk: The global Git hooks target developers specifically. Any git operation reactivates the malware, threatening source-code repositories and CI/CD pipelines.
  • Privacy Impact: The theft of the user’s profile photo adds a personal dimension to the breach. This information could be used for social-engineering follow-ups.
  • Detection Evasion: The shift to Swift and the live decryption chain may bypass existing signatures and rules trained on earlier Rust variants.

Mitigation and Recommendations

Defenders should take the following steps to reduce exposure and detect this threat.

Immediate Actions for Defenders

  1. Monitor for network connections to wavel.apple03cloudstore[.]com and the wavel[.]app domain.
  2. Inspect LaunchAgent directories for entries masquerading as com.apple.finder.agent or similar system components.
  3. Review ~/.zshrc and global Git hook configurations for unauthorized entries.
  4. Hunt for the pkgunpack binary and .sysnotif-backup.tgz archives on endpoints.
  5. Alert on processes that pause BackgroundTaskManagementAgent, BTMNotificationAgent, or NotificationCenter via SIGSTOP.

Long-Term Hardening

  • Enable and enforce Gatekeeper restrictions. The dropper relies on ad-hoc signing to bypass prompts.
  • Deploy endpoint detection and response tools with behavioral rules for JXA-to-zsh execution chains.
  • Restrict curl downloads from untrusted domains using network security policies.
  • Educate users about fake application installers, especially those delivered via cryptocurrency-themed lures.

Bottom line: The PamStealer Wavel variant raises the bar for macOS malware by tying payload decryption to live C2 sessions. Security teams must shift toward behavioral and network-based detection to catch this threat before credentials and developer environments are compromised.

Incident Summary

Incident Name: PamStealer Wavel Variant macOS Infostealer
Affected Systems: macOS devices (arm64 and x86_64)
Disclosure Date: September 22, 2026
Primary Threat Actor: Unknown operators of the PamStealer family
Attack Vector: Fake application installer (Wavel.dmg) via social engineering
Key Mechanisms: JXA dropper, X25519 key exchange, Swift infostealer, multi-layer persistence
Patch Status: No patch available — user awareness and detection controls required

References

  1. Jamf Threat Labs, “PamStealer adapts again: a move to Swift with a server-side decryption chain,” September 22, 2026, https://www.jamf.com/blog/pamstealer-wavel-macos-infostealer/ (accessed September 25, 2026).
  2. The Hacker News, “PamStealer macOS Malware Adds Live C2 Payload Decryption and Multi-Layer Persistence,” September 25, 2026, https://thehackernews.com/2026/09/pamstealer-macos-malware-adds-live-c2.html (accessed September 25, 2026).

Tags:

ExploitHackVulnerability
Author

ogwatermelon

Follow Me
Other Articles
Previous

North Korean Hackers Steal $351.6 Million from Bitget Crypto Exchange

Next

Citrix NetScaler RCE Zero-Days Under Active Exploitation

AI Botnet Breach CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network Phishing Ransomware RCE supply chain Virtualization Vishing Vulnerability Windows World Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Apple
  • BotNet
  • Breach
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerability
  • Windows
  • World
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.