Swf.exploit virus detected

Hi @Charushree,

Oh, I forgot to mention I have also tried publishing the same files on two different machines available at work and they yielded the same results unfortunately.  

I have since contacted Adobe Support with this and raised it in the bug survey that RodWard previously mentioned to me.  The Adobe Support person I was connected with acknowledged this is an issue but didn't provide any information regarding how to avoid or why it possibly has happened to me now after almost 10 years of me using capivate! (part of me has become used to not trying to understand these types of anomalies in Captivate, but the bigger part of me feels there should always be an answer!) I even supplied them links to a couple of other threads on this forum where users on previous captivate versions or programs that have SWF output i.e. Encore, have experienced the same thing and how those Adobe Support people provided resolutions by assisting them with clean up files etc.  Their response was  "Captivate is a dynamic program" and even if I make a basic change on one slide, it can have down stream impacts on your project.  I definitely am aware of this to a degree after using captivate for this long now, but as I hope you can understand, didn't feel confident or satisfied with this response or the subsequent approach to rectify my virus found dilemma.

While the Adobe Support person was excellent to provide immediate support by taking my file and having a look and identifying that some how one slide had become corrupted in one of the projects, they didn't provide confidence that this won't happen again, that I should use the latest captivate 2017.  I explained that through the  process of trying to problem solve this before I contacted Adobe, I did download Captivate 2017 and still got the same result!  In the end, they just recommended that in future if I come across this issue again, i just have to try breaking down the project and publishing at each step to try and isolate the offending slide/s.  Im sure a lot of us captivate users have had to take this approach to determine issues from time to time and know how painful and time consuming this can be, but necessary in some instances.  But for something that seems to be lying dormant in the captivate application I would hope that this could have been avoided.  Out of the four modules that got affected on the same day, this approach has worked on two of them.  On the other two, it doesn't matter which slides I have removed, or even copying and pasting various slides to another blank new project, I still get the error   So alas I am rebuilding and just hope it doesn't happen again.

This is after running a virus scan, removing any SWF files that were identified as infected with the SWF.exploit, which as just the SWFs as part of the SCORM packages for these files.

On the SCORM Cloud front, when I asked if they could help narrow down what the issue was, their developers have replied this morning to me and advised that they are white listing this virus detection and this update will be live in the platform over the next couple of days...so I guess this is a little re-assuring that it's not that bad of a 'corruption', however, our LMS wouldn't upload the same files that SCORM Cloud had flagged as being infected!  So this is a conversation I'm trying to get our LMS provider to understand at present...fun times!

In a nutshell I have been very grateful for both SCORM Cloud and the Adobe rep's responsiveness, just the solution/s still seem a bit sketchy to me and like a band aid fix.  But hopefully this will help somebody else who has the same issue.