shopify-app-bridge-internal
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-f435-6j4p-6q42
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in shopify-app-bridge-internal (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (b21c63417fe3a82fd514d0af7c913fb3c1cd62915839dc8910483fb6484bbbd9)
The package's preinstall lifecycle script in package.json runs unconditionally on npm install and issues an HTTPS GET to https://jnhwbzedabyratvgvgpgo7wtsmhsiw8d4.oast.fun/?host=shopify-<hostname>, where <hostname> is taken from os.hostname(). The oast.fun domain is a public out-of-band interaction service (interactsh) commonly used as a callback collector, so this beacon discloses the installer's machine hostname to a remote third party at install time. The package name shopify-app-bridge-internal (unscoped) with version 99.9.9 and an internal suffix is the canonical dependency-confusion shape against Shopify's official scoped @shopify/app-bridge, designed to be resolved by internal build systems that look up a private dep name against the public registry. Despite the package's self-description as a bug-bounty PoC, the install-time beacon harms any installer that resolves the name.
Source: ghsa-malware (10782d74cea89c4cb229a120caa37cc12e24845d59d5ca3f9b90f7196debbc60)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None 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