Which versions of tizen-webdriver-cli are malicious?

The following npm versions of tizen-webdriver-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tizen-webdriver-cli if I installed it?

Remove tizen-webdriver-cli 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 tizen-webdriver-cli — how do I know if it already compromised me?

If tizen-webdriver-cli 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.

Is tizen-webdriver-cli part of a known attack campaign?

Yes — tizen-webdriver-cli is associated with the IN-MAL-2026-017669 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 tizen-webdriver-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tizen-webdriver-cli (version 1.0.0).

Malicious package

tizen-webdriver-clinpm

Advisory published Aug 13, 2026Updated Aug 13, 2026

tizen-webdriver-cli is a confirmed malicious npm package (MAL-2026-13966) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tizen-webdriver-cli (npm)

MAL-2026-13966

Immediate action

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

npm uninstall tizen-webdriver-cli

What this malware does

On npm install, the package's postinstall lifecycle script collects host identifiers (os.hostname(), process.platform, process.arch, Node.js version, package name, and npm lifecycle event) and POSTs them as JSON over HTTPS to the hardcoded endpoint https://8kq1s58l.instances.poc.jchunt.top/tizen-webdriver-cli, with a 3-second timeout and errors silently swallowed. The behavior runs unconditionally at install time with no opt-in, no disclosure in normal install output, and no first-party relationship between the destination host and the package's advertised purpose (a Tizen WebDriver CLI, resembling shaka-project's generic-webdriver-server Tizen backend). The package name suggests dependency-confusion targeting of that legitimate project.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cf90f542c0f81ff50f903a216f44a5870bc0ac5ede472fa2c41af447994b58e4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tizen-webdriver-cli (version 1.0.0).
If you installed it — respond
Remove tizen-webdriver-cli 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 tizen-webdriver-cli 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. tizen-webdriver-cli 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-017669

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tizen-webdriver-cli-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