Which versions of hs-locale-management are malicious?

The following npm versions of hs-locale-management are flagged malicious: 99.99.99-poc2. Treat any of these as compromised.

How do I remediate hs-locale-management if I installed it?

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.

I already installed hs-locale-management — how do I know if it already compromised me?

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.

Is hs-locale-management part of a known attack campaign?

Yes — hs-locale-management is associated with the IN-MAL-2026-007433 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find hs-locale-management across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hs-locale-management (version 99.99.99-poc2). 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.

Malicious package

hs-locale-managementnpm

Malicious code in hs-locale-management (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6394

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall hs-locale-management

What this malware does

Package impersonates an internal HubSpot hs--scoped package using a high version (99.99.99-poc2) to win dependency-confusion resolution. On npm install, preinstall.js opens an HTTP POST to webhook.site/f83b073c-a04a-4ac5-8930-507051bd22f7 carrying the installer's hostname, current working directory, pid, OS user, platform, and a list of environment variable key names; postinstall.js sends a second beacon to the same endpoint with hostname, cwd, pid, platform, and Node version after install completes. The endpoint is an attacker-controlled webhook collector, and the package's own comments describe the behavior as a stand-in for harvesting CI/CD secrets (AWS keys, npm tokens) and source code. Both lifecycle hooks fire automatically with no user interaction.

Malicious versions

1 flagged

99.99.99-poc2

Indicators of compromise (SHA-256)

1161606183ced9cba1c4822de7f6a3515230f04ccfadd33ea2937c667cfaf1d2

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hs-locale-management (version 99.99.99-poc2). 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

No. hs-locale-management on npm has been identified as a malicious package (version 99.99.99-poc2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007433

References

npmjs.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring