Add-on Virus Notices (False Positive)
July 11, 2019
NOTE: Our add-ons do not contain any viruses.
Update: July 12th, 2019
Avast responded to our request stating that they have deactivated the "JS.Downloader" definition update they rolled out yesterday, July 11th, and their engineers are researching the issue. We will continue to monitor this but have decided to NOT roll out new versions of our software until we hear back from Avast. If you are still experiencing a false positive identification with Avast or any other anti-virus software, we recommend updating your software's virus definition files (your definition file should update automatically but if not, there should be an option/button to update them manually). If you are still seeing the warning after updating, please contact us at firstname.lastname@example.org!
tl:dr (too long, didn't read)
Some code in our add-ons is being falsely flagged as a virus. We will be rolling out updates to fix the problem as soon as we can.
On Thursday, July 11th, a world-wide virus definition update (July 11, 2019 revision 001) was released that changed some of the indicators for the "JS.Downloader" Trojan exploit that caused anti-virus software to trigger a false positive and flag our add-ons as affected.
Here is a link to more information about the "JS.Downloader" trojan, first discovered in 2003 and the "Latest Daily Certified Version" updated July 11, 2019 (at the time of this writing):
Anti-virus programs help protect you by keeping an up-to-date file that includes a list of all of the known viruses and "definitions" of what to look for to identify these types of viruses. When a definition file is updated, it is sent to a number of anti-virus software companies and downloads to your local computer. Occasionally, the definition for a virus can mistakenly identify non-virus code as a potential virus; this is what happened with some of our add-ons.
From our research, certain randomly generated strings inside our add-on's license validation protection system were being falsely identified as markers for the aforementioned virus. As the anti-virus' main objective is to keep you safe, it blocks one of the files in our add-ons, rendering them non-operational.
Only a few of our add-ons were falsely identified and we have provided a list below for you to compare your installed versions against.
What are we doing about this?
We have identified the cause of the false positive and are working on modifying our software to remove the code that matches the updated virus definitions. We will be rolling out updated versions of our software in the coming days as quickly as we can.
We also contacted the anti-virus company primarily responsible for the false positive and have requested an appropriate update to the definition so the add-ons are no longer falsely identified.
Why are there old versions in the list?
When a virus definition file is updated, it now has a new set of things to look for and even old software could be identified as malicious.
List of Affected Add-ons
|Add-on||Impacted Versions (falsely flagged with an issue)||Current Version||Current Version Falsely Flagged||Update Released|
|Assets||3.2.2, 3.2.3, 3.2.4||3.3.1||NO||NO|
|Channel Files||6.1.0, 7.0.0, 7.0.1||7.0.1||YES||NO|
|Channel Images||7.0.1, 7.1.0, 7.1.1||7.1.1||YES||NO|
|Channel Videos||5.0.0, 5.0.1||5.0.1||YES||NO|
|Charge||2.3.2, 2.3.3, 2.3.4||2.3.4||YES||NO|
|Detour Pro||2.3.1, 2.3.2, 2.3.3, 2.3.6, 2.3.7, 2.4.0, 2.4.2||2.4.3||NO||NO|
|Fieldpack||3.2.0, 3.2.1, 3.2.2||3.2.2||YES||NO|
||5.1.1, 5.1.2, 5.1.3||5.1.3||YES||NO|
|Safe Harbor||2.2.3, 2.2.4, 2.3.0, 2.3.1||2.3.2||NO||NO|
|Safe Harbor Lite||2.1.0, 3.0.0, 3.1.0||3.1.2||NO||NO|
|Structure||4.3.13, 4.3.15, 4.3.19, 4.3.20, 4.3.21, 4.3.22, 4.3.23, 4.3.24, 4.3.25, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, 4.4.5, 4.4.6, 4.5.0-b.1, 4.5.0||4.5.0||YES||NO|
|Tag||6.0.3, 6.0.4, 6.0.7, 6.0.8, 6.0.9, 6.1.0||6.1.1||NO||NO|
|Transcribe||3.0.0-b.5, 3.0.0-b.6, 3.0.0-b.7, 3.0.0-b.8, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.1.0, 3.1.1, 3.1.2||3.5.0||NO||NO|