Storyline v3.74.30180.0 course packaging infected with Malware?

May 02, 2023

About the time I installed this v3.74... update, Microsoft Teams has begun to flag the SCORM packages being produced, saying Teams has detected Malware and features are disabled.
Has anyone else seen this?

33 Replies
John Morgan

Hi Craig,

I understand you are having an issue with your SCORM packages triggering malware detection. I'm sorry you're running into this snag! I have opened a support case on your behalf. You may have seen the support email that was sent. Our support engineers will be in contact soon to help you through this issue.

Thanks for reaching out!

Melissa Leubner

I am having the same issue with some, but not all, of the files I package being flagged as malware on my client's SharePoint. When I open the URLs directly, they claim to be infected with "Phish_Gen_TiRanosBlocker_Gen#".  I have scanned them multiple times and am 99% sure it is a false positive, but if there is a way I can help the Articulate team pinpoint what exactly is causing this flag, I'd be happy to help. Sadly, simply telling my client "it's a false pos" won't help; I'm currently reverting back to an older version of Storyline to try and see if that helps.

[edit] Reverting to 3.73 did not help either. I have opened a case to try and get to the bottom of this.

Eric Santos

Hi Melissa,

Thanks for reporting this!

I see that you've connected with my teammate, John Carlo. He reported that tests using metadefender.com confirm that this is indeed a false-positive alert. Articulate has no control over it since it's only specific to SharePoint. John Carlo also suggested reaching out to SharePoint support, who can better help with SharePoint-specific issues.

Please feel free to reply to the email in your support case, but I'm happy to assist further as needed!

Ramjeet Vishwakarma

Hello Community,

My colleague and I, along with our client, are experiencing this issue. Our SCORM packages are being flagged as malware by Microsoft Teams and SharePoint.

Has anyone found a solution or workaround for this issue? Any advice or suggestions would be greatly appreciated.

Thank you in advance for your help.

Jose Tansengco

Hi Kim,

Happy to help!

We've identified that the behavior might be a false-positive flag that's happening on Sharepoint's end. You can check out my colleague Eric's response here for a test that you can do to confirm if your published output does indeed contain any malware.

Feel free to open a case with our support team here if you'd like us to dig deeper into the behavior you're experiencing.

Mata Henry

Following as we are getting the same error re "Phish_Gen_TiRanosBlocker_Gen#". Seems to be a pattern around Teams based zip file supply. I dont know what/how the system is seeing this file bc when I run a search and virus check on this file, there is no such item. 

Given other posts I've seen, this looks to be another Microsoft false positive recognising it as "Phish_Gen_TiRanosBlocker_Gen#" but is prob something else entirely unremarkable (not a virus).

Luciana Piazza

Hi Mata, 

Thanks so much for sharing what you're experiencing in this thread! If you haven't already, I recommend checking out our colleague Eric's response earlier in this thread. 

If you'd like, feel free to open a support case so we can investigate the behavior on your end! 

Have a great start to your week! ✨

BSI Learning

Hi Support, We are seeing this storyline course package being seen as Malware on our clients Sharepoint.

The following error appears:

"contains the following: "Phish_Gen_TiRanosBlocker_Gen#".

Cannot open the file at this time. For more information, contact your administrator."

We are using version September 5, 2023 (Build 3.79.30921.0).

Please advise if this can be fixed on Storyline's end as it must be something that was introduced into the packaged output to cause this as it was not happening when were publishing using the version: February 28, 2023 (Build 3.73.29904.0)

This is a high priority fix as we can't simply go to the client and say it's your SharePoint that has the problem and not the file. 

Kind regards,

Samuel @BSI Digital

 

 

Jose Tansengco

Hi Samuel, 

Happy to chime in!

If an antivirus program has outdated definitions, it may mistakenly classify a legitimate file as a false positive, which is most likely what is happening here. Another common reason for false positives is heuristic detection, which identifies potential threats based on behavioral patterns. This approach can occasionally flag legitimate files that exhibit behaviors similar to malware.

One test that you can do to confirm that your Storyline 360 course is malware free is to test using the following sites: 

If both websites confirm that the published output is malware free, then you can share this result with your client. From here, they can update their virus definitions to include the file that was falsely being flagged as malicious. 

Let me know if you have any questions!