Technically, it's not a bug. Account timestamps on Hive/Steem use UNIX timestamps: the number of seconds since 1970/01/01 UTC. All timestamps of an account are set to "0" at the beginning until they are first set to a valid value. It's maybe a bit misleading of the frontend to actually decode the "0" to 1970/01/01 instead of showing "never"...