OpenSSF/OSV advisory MAL-2026-4177 confirms this npm version as malicious. On `npm install`, the package's postinstall script runs `node -e` to fetch the installer's public IP from api.ipify.org, execute `id || ver && whoami && hostname`, and collect hostname, cwd, and USERDOMAIN/COMPANY environment variables. The bundle is POSTed to a hardcoded interactsh subdomain at lszakfghwnvxspyfcmaabd1css99rnq3w.oast.fun. The package has no legitimate function: description is 'xxx', main file...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in did-0091 (npm)
Details
On `npm install`, the package's postinstall script runs `node -e` to fetch the installer's public IP from api.ipify.org, execute `id || ver && whoami && hostname`, and collect hostname, cwd, and USERDOMAIN/COMPANY environment variables. The bundle is POSTed to a hardcoded interactsh subdomain at lszakfghwnvxspyfcmaabd1css99rnq3w.oast.fun. The package has no legitimate function: description is 'xxx', main file index.js is 0 bytes, and the only behavior is the install-time beacon. Combined with the unusual name shape, this matches dependency-confusion reconnaissance campaigns that probe corporate networks via Project Discovery's interactsh out-of-band service.
## Source: ossf-package-analysis (80bf373136eb0315910e5ba3fa9097db2cd7efe316d1defbb9b8b78f8ab8506b) The OpenSSF Package Analysis project identified 'did-0091' @ 11.0.6 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
- The package executes one or more commands associated with malicious behavior.
Decision reason
OpenSSF Malicious Packages via OSV confirms did-0091@11.2.8 as malicious (MAL-2026-4177): Malicious code in did-0091 (npm)