Which versions of localize-translate are malicious?

The following npm versions of localize-translate are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate localize-translate if I installed it?

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

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

Yes — localize-translate is associated with the IN-MAL-2026-018397 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 localize-translate 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 localize-translate (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging localize-translate across your stack and pipelines.

Malicious package

localize-translatenpm

localize-translate is a confirmed malicious npm package (MAL-2026-14279) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in localize-translate (npm)

MAL-2026-14279

Immediate action

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

npm uninstall localize-translate

What this malware does

On npm install, the package's postinstall lifecycle script collects installer host identifiers (hostname, platform, arch, node version, package name, timestamp, npm lifecycle event) and POSTs them as JSON to the hardcoded host gigww0v7.instances.poc.jchunt.top at path /localize-translate. The destination is a non-registry, author-controlled endpoint that the installer never opted into, and the beacon fires automatically at install time on every host that installs the package. The collected fields are limited to host identity (no credential, filesystem, or environment scraping is present), but the beacon is unconditional, undisclosed, and directed to a third-party host — the shape of an install-time reconnaissance callback rather than legitimate telemetry.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1a4a3b42b13a5ba692edd9761c2d32d6682f555828df49cb44e40b623861a1f0

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

Campaign

IN-MAL-2026-018397

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks localize-translate-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

Explore

All malware advisories How O3 detects malware Vulnerability database