Which versions of @tezign/html-webpack-plugin are malicious?

Every published version of @tezign/html-webpack-plugin on npm is considered malicious. Remove the package entirely.

How do I remediate @tezign/html-webpack-plugin if I installed it?

Remove @tezign/html-webpack-plugin 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 activity or persistence.

I already installed @tezign/html-webpack-plugin — how do I know if it already compromised me?

If @tezign/html-webpack-plugin 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 @tezign/html-webpack-plugin across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @tezign/html-webpack-plugin (all published versions).

Malicious package

@tezign/html-webpack-pluginnpm

Advisory published Nov 24, 2025Updated Nov 24, 2025

@tezign/html-webpack-plugin is a confirmed malicious npm package (MAL-2025-190916) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tezign/html-webpack-plugin (npm)

MAL-2025-190916

Immediate action

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

npm uninstall @tezign/html-webpack-plugin

What this malware does

The package @tezign/html-webpack-plugin was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

437929a07e5bc4e0e6dfe545fa858db027aa2ba4e6fa87701a09d5b07277b543

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @tezign/html-webpack-plugin (all published versions).
If you installed it — respond
Remove @tezign/html-webpack-plugin 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 activity or persistence.
Did it already run?
If @tezign/html-webpack-plugin 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. @tezign/html-webpack-plugin on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tezign/html-webpack-plugin-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database