omni-channel-configurator-wireline-frontend@9999.0.0

This package is malicious. It is not a real library. An attacker put it on the public npm registry. The package name is a copy of a private, internal package name. This is a dependency confusion attack. A build that gets the name from public npm installs this package in place of the real one. The package.json has a `preinstall` script. npm runs this script during install. The script file is `preinstall.js`. It runs before a person can read the code. The script collects data about the host. It reads the host name, the user name, the current directory, the install directory, the package name, the package version, the operating system, the Node.js version, and the npm user-agent text. The script sends this data to remote servers. It uses three ways. First, it makes a DNS request to a subdomain of `oast.online`. It writes the token, the package name, the host name, and the user name into the DNS name as hex text. Second, it sends an HTTPS POST with the data as JSON to the same `oast.online` host. If HTTPS fails, it uses plain HTTP. Third, it sends an HTTP POST with the same JSON to a fixed IP address, 5.189.159.252. The beacon uses a fixed token, `swisscom-oce-3b9f1c7a2e`. The `index.js` file does nothing. It is a placeholder. The code comments say this is authorized bug-bounty research. The behavior is still an unwanted install-time beacon. It sends host data to attacker-controlled servers without consent. All versions are malicious. Treat every host that installed this package as exposed. Remove the package. Look for DNS and HTTP traffic to the listed servers. --- ## Source: amazon-inspector (21d5b16b4e350d836e67410e299a1862f704c92e7bb3f26cedae46ffc7d90273) The package declares scripts.preinstall=node preinstall.js, so `npm install` unconditionally executes preinstall.js. That script collects installer identifiers (os.hostname(), os.userInfo().username, cwd, install path, process.platform, node version, npm user-agent, package name/version) and transmits them over two hardcoded channels to non-first-party destinations: an HTTP(S) POST to the Interactsh OAST callback subdomain dae7n4pijsh1ahi9684gu8get3kaiefc9.oast.online and to the bare IP 5.189.159.252, plus a DNS-tunnel channel that hex-encodes token, package name, hostname, and username as subdomain labels under the same OAST host and triggers dns.lookup. The package ships no library functionality matching its name; the preinstall beacon is the entire behavior. A self-labelled 'authorized security research / dependency-confusion PoC' string in the payload is author-controlled and does not change the observed behavior, which is a dependency-confusion exfiltration beacon fired at install time against any machine that resolves this name.