Malicious code in @ferudionz/webautomation (npm)
The npm package @ferudionz/webautomation contains malicious code that exfiltrates caller-supplied arguments (likely wallet/account identifiers) to a hidden remote URL. The package uses obfuscation and anti-debug techniques to conceal its true behavior.
- Disclosed
- Last updated
- Blast radius
- Unknown; depends on adoption of the malicious package
- Ecosystems
- Attack vectors
- Affected entities
- @ferudionz/webautomation
The npm package @ferudionz/webautomation was identified as malicious by Amazon Inspector and credited to the OpenSSF malicious-packages repository. The package exposes a single function connet(x) that POSTs the caller-supplied argument to a hardcoded remote URL.\n\nThe entire codebase is wrapped in an obfuscator.io-style RC4 string-array with a self-defending anti-debug IIFE that executes at require time. The destination URL is reconstructed at runtime from approximately 13 concatenated RC4-decoded fragments, making it invisible to static analysis. The package ships with no README, empty author metadata, and describes itself only as a generic 'logger tool'—inconsistent with its actual behavior.\n\nGiven the package name and documented usage pattern, the argument passed to connet() is likely a wallet or account identifier, meaning caller-supplied credentials are silently exfiltrated to an undisclosed author-controlled destination. The combination of hidden destination, anti-debug wrapper, and misleading cover story is inconsistent with legitimate logger or webautomation libraries.\n\nThe package has been identified and reported through official security channels (OpenSSF malicious-packages repository, advisory GHSA-66vf-3wp7-7x3j).
Indicators of compromise
- Packages
- @ferudionz/webautomation
Remediation
- Immediately uninstall @ferudionz/webautomation from all projects and environments
- Audit npm package.json and lock files for any presence of @ferudionz/webautomation
- Review any credentials, wallet identifiers, or sensitive data that may have been passed to the connet() function
- Rotate any exposed credentials or account identifiers
- Monitor for unauthorized access to affected accounts or wallets
- Use npm audit to check for this package in dependency trees
- Consider using npm package allow-lists or deny-lists to prevent re-installation
Sources
- GitHub Advisory GHSA-66vf-3wp7-7x3j · GitHub Advisory Database
Cite this entry
"Malicious code in @ferudionz/webautomation (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-ferudionz-webautomation-npm-1g7zqb
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package