Which versions of @ferudionz/webautomation are malicious?

The following npm versions of @ferudionz/webautomation are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @ferudionz/webautomation if I installed it?

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

If @ferudionz/webautomation 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 @ferudionz/webautomation part of a known attack campaign?

Yes — @ferudionz/webautomation is associated with the IN-MAL-2026-017916 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 @ferudionz/webautomation 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 @ferudionz/webautomation (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 @ferudionz/webautomation across your stack and pipelines.

Malicious package

@ferudionz/webautomationnpm

@ferudionz/webautomation is a confirmed malicious npm package (MAL-2026-14045) 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 @ferudionz/webautomation (npm)

MAL-2026-14045

Immediate action

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

npm uninstall @ferudionz/webautomation

What this malware does

The npm package @ferudionz/webautomation exposes a single function connet(x) whose sole behavior is to POST the caller-supplied argument to a hardcoded remote URL. The entire index.js is wrapped in an obfuscator.io-style RC4 string-array (_0x25ec=[...]) with a self-defending anti-debug IIFE (_0x320e22();) that runs at require time. The destination URL is reconstructed at runtime from ~13 concatenated RC4-decoded fragments, hiding it from static inspection. The package ships no README documenting a legitimate service endpoint, has empty author metadata, and describes itself only as a generic 'logger tool'. The package name and its documented usage suggest the argument passed to connet() is a wallet/account identifier, meaning caller-supplied identifiers are silently exfiltrated to an undisclosed author-controlled destination. The combination of a hidden destination, anti-debug wrapper, and a package that presents itself under an unrelated cover story is inconsistent with legitimate logger/webautomation libraries.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a55c1cc52c2e4580b15c1b9e32b436719687f489ee4ee55686aec1ec9a3adc59

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 @ferudionz/webautomation (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 @ferudionz/webautomation across your stack and pipelines.
If you installed it — respond
@ferudionz/webautomation 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 @ferudionz/webautomation 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 @ferudionz/webautomation 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. @ferudionz/webautomation 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-017916

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ferudionz/webautomation-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