tehnimax@ Thanks for the issue.

Able to reproduce this issue on Windows 10, Mac OS 10.12.6 and Ubuntu 14.04 on the latest Stable 63.0.3239.132 and Canary 65.0.3312.0.
On changing the system date to the past, the copyright year in wrench menu -> Help -> About Google Chrome is shown as the year which is set in the system.

This is a non-regression issue as it is observed from M50 chrome builds. 
Attached are the screen shot for reference.

Hence, marking it as Untriaged for updates from dev team.

Thanks...

Deleted: 798504.png 102 KB

	798504.png 102 KB View Download

Relevant code: https://cs.chromium.org/chromium/src/chrome/app/google_chrome_strings.grd?l=219

I'm inclined to say that this is probably working as intended, so that the copyright year is always current and doesn't have to be manually changed each year. I don't feel it's necessary to work around someone deliberately setting their clock wrong. That said, I don't represent the Chromium project, so the final call will be up to Chromium developers.

That confirms our suspicions. The users are indeed played for suckers. 
The programmers are too lazy to change 2 nibbles, anyway. Nothing new.

>That confirms our suspicions.
What are you suspicious about? The fact that the code calls for the current year to be used doesn't make me suspicious anyhow of Chromium.

>The users are indeed played for suckers.
If someone deliberately sets their clock wrong, what harm is it to them to have the copyright year wrong?

>The programmers are too lazy to change 2 nibbles, anyway. Nothing new.
There isn't really any reason for them to manually change the year, because they can just tell it to use the current year.

*** UI Mass Triage***

Still seeing the same issue on all OS using chrome latest Canary-72.0.3618.0. As it is non reg issue, adding respective labels.