Live › package › GHSA-r47j-grcr-p9h9
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @ecg-internal/reviews-dialog-ui | npm | all versions | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
The npm package @ecg-internal/[email protected] is a dependency-confusion payload targeting an internal @ecg-internal/* scope. package.json declares a postinstall hook (node beacon.cjs) that runs on every npm install, and beacon.cjs POSTs the installer's hostname (os.hostname()), install path (__dirname), current working directory (process.cwd()), node version, and package name over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The published main is a no-op Proxy object (module.exports = new Proxy({}, { get:... })) so consuming builds do not fail at require time, and the version 99.0.1 is set abnormally high to win semver resolution against any legitimate internal package of the same name. The scoped internal-looking name, inflated version, inert Proxy shim, and install-time callback together constitute the canonical dependency-confusion attack shape, delivering reconnaissance of the installer's build/CI environment to an attacker-controlled IP.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
This page as .md · .json · in your agent: get_signal("GHSA-r47j-grcr-p9h9")