-
Notifications
You must be signed in to change notification settings - Fork 79
problem with adware redirect to iyfnz.com site #262
Comments
I am really sorry, but I haven't been maintaining this project for several years now and I didn't renew the domain. |
Maybe you could update the README saying that the project is no longer supported, and remove all links to the spammy CDN? |
Amazon appears to have removed MSAViewer due to the malware. If you need it on your site, download and locally host http://web.archive.org/web/20190530174338id_/https://s3.eu-central-1.amazonaws.com/cdn.bio.sh/msa/latest/msa.min.gz.js or http://web.archive.org/web/20220120161943id_/https://s3.eu-central-1.amazonaws.com/cdn.bio.sh/msa/latest/msa.min.gz.js (this second link is after the malware infection date for the non-Amazon CDN, but still appears to be safe I think). You'll also need to change "at"in t to "on"in t in the downloaded file, as described here: #257 (comment) |
Updated the README. Please push my update if you can. |
Hello, we seem to have a problem with a redirect from the cdn.bio.sh file call.
Our site is redirected to the following site: http://iyfnz.com/?dn=bio.sh
We believe (though are of course not sure) that this is connected to the MSAViewer we are using for our web-site:
slim.php: <script src="//cdn.bio.sh/msa/latest/msa.min.gz.js"></script>
slim.php: <script src="https://s3.eu-central-1.amazonaws.com/cdn.bio.sh/msa/latest/msa.min.gz.js"></script>
Since it is the only web-site that is doing this re-direct, there might be a problem with the code. Any help would be appreciated.
Note: we have checked our system for adware carefully (all of them) and it is not a problem on the client side.
Thanks for your help in advance,
Bianca Habermann
The text was updated successfully, but these errors were encountered: