Author Topic: Should beacon API tracking-scripts coming from here better be blocked?  (Read 1216 times)

0 Members and 1 Guest are viewing this topic.

Offline polonus

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 33891
  • malware fighter
Specifically if you do not want to be beacom API tracked by this. Dat Peer Detector detects "eval".

Coming form -https://cdn.biddercore.io mentioned in this blocklist:
https://github.com/lassekongo83/Frellwits-filter-lists/blob/master/Swedish/src/main-hosts.txt
Detected in browser caching random example: -ttps://cdn.biddercore.io/tagman/dpg/sites/volkskrant.nl/index.js
Script being blocked by Zenmate Web Firewall for me.
Re: https://urlscan.io/domain/cdn.biddercore.io - https://urlscan.io/result/81d7d83a-afe4-497a-88e4-c72749d21751

Privacy & Security implications: https://webcookies.org/cookies/cdn.biddercore.io/28902142?831047
On server insecurity settings: https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.38

Results from scanning URL: -https://cdn.biddercore.io/tagman/dpg/sites/volkskrant.nl/index.js
Number of sources found: 216
Number of sinks found: 42

opens up to: Results from scanning URL: -https://tobias-rech.de/gluecksspiel/jquery.js
Number of sources found: 0
Number of sinks found: 0

polonus (volunteer 3rd party cold recon website security analyst and website error-hunter)



Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!