rootpwn

Malware

SHELBY Malware Uses GitHub C2 and PAT Tokens – Immediate Defender Actions

SHELBY infects machines via a phishing attachment that installs a loader which retrieves a backdoor from GitHub using a PAT token. The token grants full control, exposing a critical flaw. Defenders should block PAT token usage, monitor GitHub repos, and update detection rules.

What Happened

A phishing email from an Iraqi telecom sent a JPerf-3.0.0.exe attachment. The executable installed a benign .NET launcher that side‑loaded a malicious DLL and began communicating with GitHub for command and control.

How It Works

The loader (HTTPService.dll) pulls a value from GitHub, decrypts the backdoor (HTTPApi.dll), and loads it into memory via reflection, avoiding disk writes. Both components are obfuscated with Obfuscar, but can be deobfuscated with de4dot. The critical flaw is that any holder of the PAT token can issue commands to all infected hosts.

Impact

Both loader and backdoor have low detection rates on VirusTotal. The malware is actively developed, with unused code and dynamic payload loading suggesting future updates. The PAT token vulnerability exposes all infected systems to arbitrary control.

What to Do

  • Block outbound traffic to GitHub repositories used by SHELBY.
  • Detect and quarantine JPerf-3.0.0.exe and related files (Microsoft.Http.Api.exe, HTTPService.dll, HTTPApi.dll).
  • Implement strict PAT token management; revoke any tokens that may be compromised.
  • Use de4dot to analyze new SHELBY samples and update signatures.
  • Deploy memory‑resident detection techniques and monitor for loader activity.

SHELBY GitHub C2 PAT token Obfuscar Phishing Malware analysis

← All news