Malicious code in @convera/ui-shared (npm)
The npm package @convera/ui-shared version 0.0.2 contained malicious code that exfiltrated system hostname and username during installation via a preinstall script. The package was published under a private namespace scope, creating a dependency-confusion attack surface against the Convera organization.
- Disclosed
- Last updated
- Blast radius
- Any developer or system that installed @convera/ui-shared version 0.0.2 from npm.
- Ecosystems
- Attack vectors
- Affected entities
- @convera/ui-shared · 0.0.2
The npm package @convera/ui-shared version 0.0.2 was identified as malicious by both Amazon Inspector and the OpenSSF Package Analysis project. Upon installation, the package's preinstall.js script executed code that collected the system hostname via os.hostname() and the current user via os.userInfo().username, then transmitted this information as query parameters to am0f14nl6o1nqwrngbrq33amfdl496xv.oastify.com, a Burp Collaborator subdomain.\n\nThe package was published under the @convera/* scope, matching a private internal namespace used by the Convera organization. This created a dependency-confusion attack surface: developers or systems that misconfigured their registry settings or accidentally resolved the public npm version instead of an internal private registry would silently install the malicious package. The package contained no functional code beyond the exfiltration mechanism, shipping only an empty index.js file.\n\nThe package description identified itself as a 'bug-bounty research placeholder — Convera', though regardless of stated intent, the unauthorized collection of host identifiers from every installer constitutes a supply chain attack. The malicious activity was detected and the package has been removed from npm.\n\nCredits: Amazon Inspector, OpenSSF Package Analysis project, and OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- @convera/ui-shared@0.0.2
- Domains
- am0f14nl6o1nqwrngbrq33amfdl496xv.oastify.com
Remediation
- Immediately uninstall @convera/ui-shared from all systems and projects
- Audit npm install logs and package-lock.json files to identify any installations of version 0.0.2
- Assume any system that installed this package had hostname and username exfiltrated; consider this a potential reconnaissance event
- Review network logs for outbound HTTPS connections to am0f14nl6o1nqwrngbrq33amfdl496xv.oastify.com during the installation window
- If using the @convera scope internally, configure npm registry settings to prevent accidental resolution from the public npm registry
- Monitor for any follow-up attacks or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-5gr4-vr9v-phc3 · GitHub Advisory Database
Cite this entry
"Malicious code in @convera/ui-shared (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malicious-code-in-convera-ui-shared-npm-9lyjl6
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in @pelmnaads/naads-common-logger (npm)
Malicious code in @pelmnaads/naads-common-logger (npm) version 19999.0.1 exploited dependency confusion by publishing to the public npm registry with an abnormally high version number. A preinstall script transmitted installer hostname data to a Burp Collaborator endpoint (h5nvwrz2815ubw84cpkwhezm5db9z1nq.b.mburpcollab.com), silently exfiltrating build host identity.
npmDependency confusionCompromised package - containedcritical
Malicious code in secdriven (npm)
The npm package 'secdriven' version 1.0.8 contains malicious postinstall code that exfiltrates host identity, username, working directory, and CI environment variables to a third-party OOB-detection endpoint. The package is a dependency-confusion payload targeting Google's internal namespace, masquerading as a security research canary.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in @webapp-next/store (npm)
The npm package @webapp-next/store contained malicious code that executed automatically on installation, collecting system and user information and exfiltrating it to an attacker-controlled server. The package had no legitimate functionality and used a dependency-confusion lure with a scope resembling a legitimate namespace.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @design-system-coopeuch/web (npm)
@design-system-coopeuch/web versions 999.0.4 and 999.0.0 on npm contained malicious code implementing a dependency-confusion attack. The package included a preinstall hook that exfiltrated host identifiers (hostname, working directory, user ID, environment variables) to a hardcoded IP address via cleartext HTTP.
npmDependency confusionCompromised package