A small bug introduced in the code based in the end of May. Not sure of exactly when it was released, wasn't worth the time to figure out. A fix has been made, the data for this geocache has been corrected, we'll queue jobs to fix other potentially affected geocaches.
In the end it's related to privacy protected accounts.