Malicious code in @ferudionz/web_logger_js (npm)
The npm package @ferudionz/web_logger_js contained obfuscated malicious code that exfiltrates caller arguments to an attacker-controlled endpoint. The package exports a single function that unconditionally sends its input to a hardcoded URL hidden behind RC4 encryption and anti-debug wrappers, targeting potential EVM/crypto account credentials.
- Disclosed
- Last updated
- Blast radius
- Any application that installed and called the @ferudionz/web_logger_js package
- Ecosystems
- Attack vectors
- Affected entities
- @ferudionz/web_logger_jsnpm package containing malicious code
The npm package @ferudionz/web_logger_js was published with intentionally obfuscated malicious code designed to exfiltrate sensitive data. The package uses obfuscator.io-style techniques including a rotated string array, RC4 key-schedule encryption, XOR string decoding, and anti-debug wrappers to conceal its true behavior from static analysis.
The package exports a single function connet(x) that unconditionally issues an HTTP GET request via axios to an attacker-controlled endpoint. The destination URL is assembled at runtime from approximately 13 RC4-decoded fragments, and the require target and HTTP method are similarly reconstructed from ~130 encoded literals at runtime. This runtime reconstruction prevents static inspection tools from identifying the malicious behavior.
Any consumer calling the package's public API will silently exfiltrate their input argument to the hardcoded author-controlled destination without any configuration or user awareness. The package name mismatch with its documented install string (npm install evm_account) and the nature of the exfiltration suggest targeting of EVM/cryptocurrency account identifiers, addresses, or key material.
The concealment techniques—RC4 decoding, anti-debug wrapping, and proxy functions—rule out accidental or undocumented behavior, indicating intentional malicious design by the package author.
Indicators of compromise
- Packages
- @ferudionz/web_logger_js
Remediation
- Immediately uninstall @ferudionz/web_logger_js from all projects
- Audit all applications that installed this package for any calls to the connet() function
- Review logs and network traffic from affected systems for exfiltration to unknown endpoints
- Rotate any credentials, keys, or sensitive account identifiers that may have been passed to the package
- Check npm audit and dependency scanning tools for this package in your supply chain
- Report the package to npm security for removal and account investigation
Sources
- GitHub Advisory GHSA-wjf7-fv2q-889h · GitHub Advisory Database
Cite this entry
"Malicious code in @ferudionz/web_logger_js (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-web-logger-js-npm-tyxcbv
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package