Malicious code in hyperpure-core (npm)
-= Per source details. Do not edit below this line.=-
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.
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도(기본값(정보 없음)) | 55.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 55.00 |
VPI 공식 vpi-v1 기준