Other features as well
Chrome 68 includes two anti-malvertising features
The biggest of these, at least on the security front, are Chrome's new blocking mechanisms for tactics often employed by online malvertisers.
For example, Chrome now blocks shady iframes (which are embedded on a page) from redirecting the entire parent page to another URL. These changes have been slowly implemented
since Chrome 64 and have now been rolled out in full.
The only way an iframe will be allowed to redirect the main page to a new URL is only if the user has directly interacted with the iframe. Since most iframes used in malvertising campaigns are usually placed off-screen, this change should block malicious ads from redirecting users to new sites, while still allowing single-sign-on (SSO) login pages or similar technologies to work as intended.
Second, Chrome now also fully blocks tab-under behavior. Tab-under is when users click on a link, but a shady website opens the URL in another tab and keeps the old tab alive, while also using the old tab to load another URL with a bunch of ads. The tab-under technique is found all over the web and has become a problem in recent years.
Google first announced tab-under blocking
last year, and it rolled out a first tab-under blocking mechanism
in Chrome 65. Today, Google is making a formal announcement of this feature, which will show warnings like the one below every time it blocks a shady site trying to duplicate its tab and use one to show ads.
Chrome 68 is also another milestone, but on another security front. Chrome 68 represents Phase 2 of Google's larger plan of preventing third-party software (mostly antiviruses) from injecting code into the main Chrome process. As Google explained
last November:
Chrome 68 will begin blocking third-party software from injecting into Chrome processes. If this blocking prevents Chrome from starting, Chrome will restart and allow the injection, but also show a warning that guides the user to remove the software.
Google plans to remove the ability to inject third-party code into Chrome and block this behavior altogether starting with January 2019.
Read more here
Chrome 68 Released With Warnings on HTTP Sites, But Also Other Security Features