Information about this bug is on GitHub and was touched in in the News release with 2.0.15. However, we're not certain modders are clear on the implications, so we wanted to toss up an announcement ensure adequate attention was brought to the issue.
This notice affects modders. Specifically, those who edited DLC files with ME3Explorer v2.0.5-2.0.14, released between 23 May 2016 and 21 Sept 2016. The bug is fixed in v2.0.15/3.0.
These versions contained a change to save methods that affected DLC files (with a shadercache) in an adverse way. As explained by kinkojiro on GitHub, modding these files with textures will corrupt them. Which means if your users scan on them and attempt to texture mod them, they will become corrupted and unusable.
Base game files are unaffected, and, as far as I know, DLC files without a shadercache will also be unaffected.
For modders who edited DLC files during this time frame with these versions of the toolset, you should check to see if any have a shadercache. If so, then they likely contain this bug and should be re-made using v3.0.
If you have modded any DLC files without removing the shadercache this will impact you. Using texplorer earlier than 2.0.15 on a modded DLC file saved using 2.0.5 or later is likely to result in the file getting turned into garbage. The safest route is to insist that all users use ME3Explorer 3.0 or later.