Which versions of @productdevbook/ts-i18n are malicious?

The following npm versions of @productdevbook/ts-i18n are flagged malicious: 1.4.2. Treat any of these as compromised.

How do I remediate @productdevbook/ts-i18n if I installed it?

@productdevbook/ts-i18n 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 @productdevbook/ts-i18n — how do I know if it already compromised me?

If @productdevbook/ts-i18n was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @productdevbook/ts-i18n across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @productdevbook/ts-i18n (version 1.4.2).

Malicious package

@productdevbook/ts-i18nnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@productdevbook/ts-i18n is a confirmed malicious npm package (MAL-2025-191305) that steals credentials and exfiltrates sensitive data (malicious version 1.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @productdevbook/ts-i18n (npm)

MAL-2025-191305

Immediate action

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

npm uninstall @productdevbook/ts-i18n

What this malware does

The package @productdevbook/ts-i18n was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.4.2

Indicators of compromise (SHA-256)

a3a179f73cb9539932849e140a3174fed56fa172ebd9fcc8c680e791bf95566d

b3152cc79cb103f8af6266254c613952272ccb9481db9fb8f299a3fdfa6db7a9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @productdevbook/ts-i18n (version 1.4.2).
If you installed it — respond
@productdevbook/ts-i18n 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 @productdevbook/ts-i18n was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @productdevbook/ts-i18n on npm has been identified as a malicious package (version 1.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @productdevbook/ts-i18n-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