Malicious code in goldenflow-js (npm)
MAL-2026-11463 · GHSA-7gxf-x4v3-6vq7
Published · Modified
Dependency scanning
Check whether goldenflow-js is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (a8634bdafa282ed99ee4b3edd205599207ac2f52a4d150d4bdd0f9b69326f64d)
lib/report.js in goldenflow-js@1.0.0 collects installer-side data using node's os, child_process, and fs modules (os.hostname(), os.userInfo(), execSync-derived output, and fs.readFileSync on local files) and transmits it via https.request POST to a hardcoded external endpoint at hooks.zapier.com (referenced at lib/report.js line 12, request built at line 118, POSTed at line 121). The destination is an author-controlled Zapier webhook rather than any first-party or user-configured endpoint, and the payload combines host identifiers, user account information, command output, and file contents read from the installer's filesystem.
Source: ghsa-malware (d6d0c7798c31f2743649318d78a1937fd28af9e4c28a2808046b647f2c087568)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes