Malware in @webda-infra/search
Malware was discovered in the npm package @webda-infra/search. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @webda-infra/search
A malware incident was identified in the npm package @webda-infra/search, published as GitHub Advisory GHSA-4rmm-f927-v58w on June 29, 2026.\n\nAny computer with this package installed or running is considered fully compromised. The malware grants outside entities full control of affected systems, enabling potential theft of secrets, keys, and other sensitive data.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- @webda-infra/search
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @webda-infra/search package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging or replacement if the package was installed on production or sensitive systems
- Notify any downstream users or services that may have been affected by the compromise
Sources
- GitHub Advisory GHSA-4rmm-f927-v58w · GitHub Advisory Database
Cite this entry
"Malware in @webda-infra/search." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-webda-infra-search-h3qmej
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