@myorder-frontend-commons/analyticsnpm

Package is published to the public npm scope @myorder-frontend-commons and declares preinstall, install, and postinstall lifecycle scripts all set to node poc.js, so the payload auto-executes on any npm install that resolves this scope. poc.js collects host identifiers (os.hostname(), os.userInfo().username, os.platform()/arch/release, process.cwd(), node version, package metadata, and names of CI-related environment variables) and transmits them via HTTP GET to a hardcoded Interactsh out-of-band subdomain at db4jftohu4noreqdanngpnb3ger45ykrt.oast.fun and a hardcoded IP-based backup collector at 80-190-83-27.nip.io, plus a hex-encoded DNS-label beacon containing the hostname, user, and version. index.js exports stubs that mirror the API shape of an internal package of the same name, which is the dependency-confusion lure: an internal build system that mistakenly resolves against the public registry will install this package and immediately execute the beacon. The payload satisfies the installer-harm gate (install-time code execution plus host-identifier exfiltration to third-party collectors) regardless of any "authorized PoC" framing, because the installer did not consent and the destinations are not controlled by the installer.

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.

The OpenSSF Package Analysis project identified '@myorder-frontend-commons/analytics' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

• The package communicates with a domain associated with malicious activity.