hyperpure-corenpm
Advisory published Updated
hyperpure-core is a confirmed malicious npm package (MAL-2026-6250) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hyperpure-core (npm)
What this malware does
Package impersonates a Zomato internal namespace (name hyperpure-core, repository URL pointing to github.com/zomato/hyperpure-core) while shipping a 63-byte stub index.js that exports nothing functional. The package.json preinstall (and preuninstall) lifecycle script runs at npm install time and uses curl to POST the installer's hostname -f, whoami, current working directory, and the full env output (base64-encoded) to http://d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site over plaintext HTTP. On CI / developer machines the captured environment routinely contains credential-grade values (AWS_*, NPM_TOKEN, GH_TOKEN, CI provider secrets), so this is unambiguous installer-side credential and host-identity exfiltration. The shape (internal-name impersonation + hollow module + env-leaking preinstall + OAST out-of-band callback) is a textbook dependency-confusion attack against Zomato build infrastructure.
The OpenSSF Package Analysis project identified 'hyperpure-core' @ 1.0.0 (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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for hyperpure-core (version 1.0.0).
If you installed it — respond
hyperpure-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hyperpure-core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks hyperpure-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.