Pretty standard for a company to defend its trademark, indeed NPM sided with them. The article you link to places the blame for that "npm havoc" solely with th

Pretty standard for a company to defend its trademark, indeed NPM sided with them. The article you link to places the blame for that "npm havoc" solely with the contributor you mention. >Under our dispute policy, an existing package with a disputed name typically remains on the npm registry... >In this case, though, without warning to developers of dependent projects, Azer unpublished his kik package and 272 other packages. >It was abrupt unpublishing, not our resolution policy, that led to yesterday’s disruptions.