If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (2adb7ba5ebcb66930ae574353088696c939ed6e677c12437e78de7166e96b932)
Package self-identifies in package.json as a dependency-confusion proof-of-concept targeting HubSpot's internal `hs-locale-management` namespace, published at the high-watermark version 99.99.99 to outrank any internal release during npm resolution. The postinstall.js script collects local host fingerprint data (os.hostname(), os.userInfo().username, platform, node version, pid) and prints it to stdout — it does not exfiltrate over the network, drop additional payloads, read credentials, or modify the installer's filesystem outside its own package directory. Installer impact in this version is limited to a harmless console print during `npm install`. The supply-chain concern is structural: any HubSpot build pipeline (or third party who mistakenly resolves this name from the public registry) executes this package's lifecycle scripts, and the same publishing position can be reused to ship arbitrary code in a future version. Routing to human review per policy on namespace-abuse / squat-name packages — present-version harm does not meet the block bar, but the squat itself warrants maintainer or registry-side action (takedown / namespace reservation).
Source: ghsa-malware (c0c64cbd2dc6ed9daff15a5552b386ab39a761b8a7fb212d3ee60c1c91a2605c)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.