Which versions of goldenflow-js are malicious?

The following npm versions of goldenflow-js are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate goldenflow-js if I installed it?

Remove goldenflow-js from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed goldenflow-js — how do I know if it already compromised me?

If goldenflow-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is goldenflow-js part of a known attack campaign?

Yes — goldenflow-js is associated with the GHSA-7gxf-x4v3-6vq7, IN-MAL-2026-011225 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find goldenflow-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for goldenflow-js (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging goldenflow-js across your stack and pipelines.

Malicious package

goldenflow-jsnpm

goldenflow-js is a confirmed malicious npm package (MAL-2026-11463) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in goldenflow-js (npm)

MAL-2026-11463

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall goldenflow-js

What this malware does

lib/report.js in [email protected] 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.

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d6d0c7798c31f2743649318d78a1937fd28af9e4c28a2808046b647f2c087568

a8634bdafa282ed99ee4b3edd205599207ac2f52a4d150d4bdd0f9b69326f64d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for goldenflow-js (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging goldenflow-js across your stack and pipelines.
If you installed it — respond
Remove goldenflow-js from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If goldenflow-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks goldenflow-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. goldenflow-js on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7gxf-x4v3-6vq7IN-MAL-2026-011225

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks goldenflow-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database