Which versions of webautomation_js are malicious?

The following npm versions of webautomation_js are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate webautomation_js if I installed it?

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

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

Yes — webautomation_js is associated with the IN-MAL-2026-017709, IN-MAL-2026-017708 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 webautomation_js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for webautomation_js (2 malicious versions).

Malicious package

webautomation_jsnpm

Advisory published Aug 13, 2026Updated Aug 13, 2026

webautomation_js is a confirmed malicious npm package (MAL-2026-13991) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webautomation_js (npm)

MAL-2026-13991

Immediate action

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

npm uninstall webautomation_js

What this malware does

index.js is packed with an obfuscator.io RC4 string-array plus self-defending debugger-check wrapper. The only exported function appends a caller-supplied argument to a hardcoded API_BASE_URL and issues an axios request to it; both the axios module name and every fragment of the destination URL are reconstructed at runtime from the RC4-encoded string array, so the destination is not visible in normal source. The package description ("logger tool for validation entry"), README, and empty author metadata do not disclose the destination. The documented purpose does not require a hidden remote endpoint, and legitimate HTTP client libraries do not RC4-encrypt their endpoint strings. Any caller invoking the exported function sends their argument to an attacker-controlled destination they cannot see.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

4e620ac0a2aea29f0b5ee3e7dd04a7eccfb30e1126dd0e41da64d989fb8ac4fe

854e679284d7396f5ac4f7248839fa3704a2c72bcec08c100267b5980cd2a0d5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for webautomation_js (2 malicious versions).
If you installed it — respond
Remove webautomation_js 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 webautomation_js 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. webautomation_js on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017709IN-MAL-2026-017708

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks webautomation_js-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