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?

Remove localization-lib from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is localization-lib part of a known attack campaign?

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

Can O3 Security detect localization-lib in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking localization-lib and packages like it before any post-install script runs.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

bcd25156cfc8d9cd6b46f2b84b7212acd8a139ae38c964302332104a0fb44067

bf143361939feffe7099c14acc7cf41a401681481e932e15d6054dde49e88f94

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-005031

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection