Once you know that your code has been corrupted, it would take a team of consultants put together by someone like ptacek a relatively short period of time to find the holes (and, at the same time, discover 10x or more  code weaknesses that weren&#x27;t deliberately put there.)<p>If the toolchain wasn&#x27;t corrupted, and this was in the original source code (C?) - it&#x27;s not going to be too difficult to find in code review, <i>if you are looking for it</i> - but how many companies are willing to spend the time (and $$$) to review their presumed secure code for holes added by third-parties?<p>Now that Juniper knows that their source-code&#x2F;tool chain has been breached, they will be prepared to spend the money to clean it up - which, for any reasonable amount of code, will cost millions of $$$ if not tens of millions.<p>I&#x27;m wondering if patio11&#x2F;ptacek didn&#x27;t show some pretty amazing foresight in tracking down the resumes of the top security intrusion people in the industry - I have to believe that the Ciscos, Junipers, and other security hardware&#x2F;software companies in the world are going to be in desperate need of Top People, and are going to be ready to pay large sums of $$$ for fast service in this space.