An attacker with high privileges (but perhaps needing to maintain long-term, hidden access) adds a non-existent SID to a resource's ACL.
Standard security tools often monitor for changes to ACLs for existing users. Since the injection happens before the user exists, it can bypass traditional monitoring. An attacker with high privileges (but perhaps needing
A low-level account created later can suddenly "wake up" with Administrative or Domain Admin rights if those rights were pre-injected into the synthetic SID. A low-level account created later can suddenly "wake
These synthetic entries often appear as "Account Unknown" or long strings of numbers in the security tab, which administrators frequently ignore as remnants of deleted accounts rather than active threats. Because the system allows adding SIDs that aren't
The vulnerability relies on the way Windows handles SID resolution. Because the system allows adding SIDs that aren't yet mapped to a user, the ACL essentially waits for its "missing half".
Yes, identified a technique known as Synthetic SID Injection .
Once a new user or group is created and assigned that specific SID, they automatically inherit all the "synthetic" permissions previously injected, often without appearing in standard audit logs as a new permission grant. Why This Matters