pandafortunerush
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-m4h2-gmhc-mhcp
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in pandafortunerush (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (6aad00d10629d1eb8787b0f86fef826926298e9392bd0a5289450eb73cf5f549)
[email protected] declares both preinstall and postinstall lifecycle scripts that issue plain-HTTP GET requests to http://38.242.235.206/depconf/pandafortunerush/{preinstall,postinstall}, carrying the installer's username (process.env.USER / USERNAME), OS hostname (os.hostname()), and current working directory (process.cwd()) as query parameters. The requests fire automatically on npm install with no caller consent. The package self-describes as a defensive dependency-confusion placeholder for an internal project name, but ships no functional code — its only runtime effect is the install-time beacon of installer identity to an unrelated bare-IP destination. The destination is not a registry, publisher-matched host, or documented telemetry endpoint; sending installer host identifiers to it on install discloses internal hostnames, usernames, and build-path layout useful for targeting follow-on attacks against the installing organization.
Source: ghsa-malware (019d3c32de84d0958b6b15bdf73d9ba7813e7bc9ded749be0e44320d81d28afe)
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