Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to malware
MalwareUsed by 1 actor

IRAOAuth2.0

IRAOAuth2.0 is a malicious NuGet package used in a software supply-chain campaign targeting ASP.NET web application developers. It was one of four related packages published between August 12 and 21, 2024 by the NuGet account "hamzazaheer"; the others were NCryptYo, DOMOAuth2_, and SimpleWriter_. The campaign accumulated more than 4,500 downloads before the packages were removed following responsible disclosure.

IRAOAuth2.0 is a companion payload in a multi-package attack chain. The campaign activates only after all four packages are installed. NCryptYo functions as the stage-1 dropper, executing on assembly load, installing JIT hooks, decrypting embedded payloads, and deploying a stage-2 localhost proxy on 127.0.0.1:7152. IRAOAuth2.0 then communicates with that local proxy rather than directly with attacker infrastructure; the proxy relays traffic to an external C2 whose address is dynamically resolved at runtime.

Its primary capability is exfiltration and manipulation of ASP.NET Identity authorization data. Researchers reported that IRAOAuth2.0 transmits ASP.NET Identity data, including user accounts and role/permission mappings, through the local proxy to attacker-controlled infrastructure. It implements the same four data exfiltration endpoints as DOMOAuth2_, corresponding to get-permissions, get-role-permissions, update-role-permissions, and update-user-permissions. The C2 can return authorization rules that are processed by the victim application, enabling persistent backdoors such as granting admin roles, modifying access controls, or disabling security checks in deployed applications.

IRAOAuth2.0 removes configurability compared with DOMOAuth2_. It ignores any caller-provided AuthKey and instead inlines a hardcoded authentication token. Reporting also states that DOMOAuth2_, IRAOAuth2.0, and SimpleWriter_ share a byte-identical embedded credential that decodes to a common API key and ProjectId used to authenticate to the same C2 infrastructure. The decoded ProjectId was reported as 06062730-b307-48a6-a7c3-140e6bae4587, and the Auth string begins with "9ujkh@(ik#@!mpoid-0ePpasj@onbxwWmi@lllmcoPiKe...".

Additional reported artifacts linking IRAOAuth2.0 to the broader campaign include shared build metadata and source path exposure. Assembly metadata indicated builds on Windows NT 10.0.22631 using NuGet Pack 6.10.0.97 with LangVersion 12.0 and unsafe code enabled. Exposed PDB paths included E:\Projects\A-Mark\Authorization\OAuth2.0\ for DOMOAuth2_ and IRAOAuth2.0, supporting common authorship across the package set. Researchers also noted that IRAOAuth2.0 references a dependency named Shared v1.0.0 for model types not present in the public NuGet package "Shared" by EagleTM, suggesting a broken or private dependency.

The reported objective of the campaign was not primarily to compromise developer workstations directly, but to compromise ASP.NET applications built with the malicious dependencies so that production deployments continue exfiltrating authorization data and accepting attacker-controlled permission changes.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
hamzazaheer

"IRAOAuth2.0 implements the same four data exfiltration endpoints as DOMOAuth2_ but removes all configurability."

via socket blogsocket.dev
MITRE ATT&CK

Techniques & procedures

8 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

2 techniques
T1195.001Compromise Software Dependencies and Development ToolsEvidence2

“A supply chain attack targeting ASP.NET developers… involving four malicious NuGet packages… NCryptYo… typosquatting the widely used NCrypto package.”

T1195.002Compromise Software Supply ChainEvidence1

"Socket's Threat Research Team discovered a NuGet supply chain attack involving four malicious packages... The lead package NCryptYo masquerades as a cryptography library through deliberate typosquatting of the legitimate NCrypto package."

Persistence

1 technique
T1136.003Cloud AccountEvidence1

"received authorization rules to create backdoors, granting attackers administrative access"

Collection

1 technique
T1005Data from Local SystemEvidence1

“DOMOAuth2_ and IRAOAuth2.0 silently collect ASP.NET Identity data — user account IDs, role assignments, and permission mappings — and route it to the attacker’s server”

Command and Control

2 techniques
T1071.001Web ProtocolsEvidence1

"the package sends HTTP POST requests to https://localhost:7152/api/auth/... Every request includes the hardcoded auth token in an HTTP header."

T1572Protocol TunnelingEvidence1

"deploy a stage-2 binary - a localhost proxy on port 7152 that relays traffic... to the attacker's external C2 server"

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence2

“route it to the attacker’s server through the local proxy.”

Other

1 technique
T1562Impair DefensesEvidence1

"or disabling security checks"

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution1

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping8

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.