It&#x27;ll be interesting to see a more in-depth look at the code surrounding this and some theories on how it could have been implemented in a way that avoided obvious detection.  The naive assumption is that someone just added to the code:<p><pre><code>    if(!strcmp(password, &quot;&lt;&lt;&lt; %s(un=&#x27;%s&#x27;) = %u&quot;)) return true;
</code></pre>
which is certainly possible, but seems too easily detectable and risky for someone on the inside, and too lazy for someone on the outside that had already gone through the trouble to get write access to the source.<p>The string itself looks like it&#x27;s part of some logging system, so my guess is that it already existed and was opportunistically chosen rather than created.  If this was passed through a macro, then it&#x27;s possible that the attacker didn&#x27;t have to touch the auth code at all and may have been able to implement this by changing only a handful of characters in an area of code that was more amenable to obfuscation.