This issue was apparently introduced earlier this year during an update. It will be corrected for all basemaps that show this in the next update coming in early April. Note that Living Atlas basemap updates (and other content updates) are not coupled to ArcGIS Online updates, rather they happen at their own cadence.