Does that still happen if you try again (it might have been a network problem).
Otherwise all I can think of is that the npm cache is corrupted, though that is very unusual. If trying again fails the same way then run npm cache clean --force
and try again.
What version of npm have you got? According to https://docs.npmjs.com/cli/cache it is supposed to be not possible to get corrupted data in the cache. To find out run npm -v
also of interest might be node -v