I posted a month ago about this, pertaining to an update that was rolled out that caused the devices (flexes in particular) to become 'tampered' after the critical file was pushed. This contradicts the diagnostics screens and the developer section during provisioning.
Seeing that some of the threads are blowing up about it, seems like it's back to that again, especially with the same issue, it's happening again so it seems.
This time around, it appears to be only instigated during the provisioning cycle. You may want to issue a hotfix or a rollback to the previous version. Cause this happened twice within a 3 month span, it's becoming a major concern now.
So what gives?