취약점

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (17328047b2ec8dce82cfbdfd5b16c8f862d51dca26b02c9801587c220a48975a)

On npm install, postinstall.js collects host identifiers (os.hostname, os.userInfo username, os.platform, current working directory, CI environment variable, and package name/version) and sends them as query-string parameters in an HTTPS GET to a hardcoded webhook.site collector URL (postinstall.js line 18: https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5?pkg=...&host=...&user=...&platform=...&cwd=...&ci=...). The fetch fires automatically on install and errors are silently swallowed. The package self-describes as a 'defensive typo-squat' research artifact, but installer-side identifiers are exfiltrated to a third-party request collector without consent regardless of stated intent. The package name pattern targets users who mistype an ESLint rules package, increasing the chance of unintended installation.

Source: ghsa-malware (475d9167eb060364b156fd3187b6adcf907ef787757f600b94dcb312b505ee0c)

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.