hs-locale-managementnpm
hs-locale-management is a confirmed malicious npm package (MAL-2026-6394) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 99.99.99-poc2, 99.99.99-poc3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hs-locale-management (npm)
What this malware does
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).
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hs-locale-management (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hs-locale-management across your stack and pipelines.
If you installed it — respond
hs-locale-management is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hs-locale-management was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks hs-locale-management before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks hs-locale-management-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.