blinkit-core
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in blinkit-core (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (2ca70b0a6be36daf245deb50dd6b3595a9bfba29c62770e82365152a02832cf8)
On npm install, the package's preinstall lifecycle hook runs curl against http://d8s0b82plbq3u5sb2vo0sb3a9obr4yjt7.oast.site/ and POSTs the installer's hostname (hostname -f), current user (whoami), working directory, and a base64-encoded dump of the entire process environment (env | base64 -w0) — which on CI/build hosts routinely contains tokens, cloud credentials, and registry auth. The package itself is hollow: index.js only exports { name, version } and provides no functionality. The repository.url claims git+https://github.com/zomato/blinkit-core.git while publishing under that internal-sounding name on the public registry, matching the canonical dependency-confusion attacker shape against Zomato's internal blinkit-core namespace. Installer harm: any build pipeline that resolves this public package instead of an internal mirror leaks host identity and the full environment (including secrets) to the attacker's out-of-band interaction listener at install time, before any other code runs.
Source: ossf-package-analysis (304234c334dce7d26c040f318d608e24b53db9b0b7b0b27d3a6dd2c040481b15)
The OpenSSF Package Analysis project identified 'blinkit-core' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
Not rated by the source.
1.0.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0