The package's postinstall.js runs at install time and performs a credential-harvest + host-tampering chain against the installer. It enumerates npm credentials by calling npm config get for keys including _authToken, _auth, registry, //registry.spectral-corsair.htb:1337/:_authToken, //registry.spectral-corsair.htb/:_authToken, and //154.57.164.64:32271/:_authToken, dumps the full npm config list --json, and reads /usr/lib/node_modules/npm/.npmrc, /etc/hosts, /app/.bowerrc, /root/.bowerrc, and source files under /app (Cargo.toml, main.rs) plus filesystem-wide flag/secret greps. The collected output is base64-encoded and HTTP PUT to a hardcoded bare IP http://154.57.164.64:32271/api/modules/.... Separately, postinstall.js appends 154.57.164.64 registry.spectral-corsair.htb to /etc/hosts when not already present, then queries the spoofed registry via curl and npm view — install-time host-file tampering that redirects a registry hostname to an attacker-controlled IP and enables later package substitution / MITM. Execution is gated by an anti-analysis shouldRun() that bypasses CI environments (GITHUB_ACTIONS, RUNNER_OS, CI), Chinese registry mirrors (npmmirror, tencent, cnpm, taobao), and /tmp working dirs, and only fires when the hostname matches a 12-hex Docker short-id pattern and cwd contains /app — narrow targeting that confirms intent while shipping the malicious code unconditionally.

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 'coral-wraith' @ 6.0.0 (npm) as malicious.

It is considered malicious because:

• The package executes one or more commands associated with malicious behavior.