Malicious code in golaaa (npm)
The npm package golaaa contains malicious code that launches a local browser with remote debugging enabled, intercepts user input and page content via Chrome DevTools Protocol, and exfiltrates captured data to an attacker-controlled Cloudflare Worker endpoint. Credentials are obfuscated using XOR-then-base64 encoding to evade static inspection.
- Disclosed
- Last updated
- Blast radius
- Any application using the golaaa npm package; all data accessible in the debugged browser context (page content, keystrokes, credentials, API keys).
- Ecosystems
- Attack vectors
- Affected entities
- golaaanpm package containing malicious code
The npm package golaaa was published with embedded malicious code designed to exfiltrate sensitive data from applications that use it. When executed, the package launches a local browser instance with remote debugging enabled on port 9222 and connects via the Chrome DevTools Protocol (CDP).\n\nThe malicious payload disables Content Security Policy protections and injects a persistent script that intercepts window.fetch calls, logs all keyboard input, and captures the full text content of the page body and active DOM elements. This captured data is base64-encoded and sent via HTTP POST to a hardcoded endpoint: https://ai-script.test0ing7.workers.dev/, which is hosted on an attacker-controlled Cloudflare Worker.\n\nThe package ships two API keys as obfuscated XOR-then-base64 blobs, reconstructed at runtime using the function _xd(s,x)=Buffer.from(s,'base64').map((b,i)=>b^x.charCodeAt(i%x.length)) with the hardcoded key 'Mx7rLp2Qn'. This obfuscation prevents static code analysis from revealing the credentials. Critically, there is no configuration option to redirect the exfiltration endpoint, meaning all intercepted data flows through the attacker's infrastructure regardless of the package's documented purpose.\n\nThe combination of hardcoded relay endpoints, credential obfuscation, and lack of user control over data destination indicates deliberate concealment of the malicious dataflow. The incident was identified by the OpenSSF malicious packages project.
Indicators of compromise
- Packages
- golaaa
- Domains
- ai-script.test0ing7.workers.dev
Remediation
- Immediately remove the golaaa package from all projects and dependencies.
- Audit all systems where golaaa was installed for signs of data exfiltration or unauthorized access.
- Rotate any API keys, credentials, or sensitive data that may have been exposed to systems running golaaa.
- Review browser history and network logs on affected systems for connections to ai-script.test0ing7.workers.dev.
- Use npm audit to identify and remove any other malicious or compromised packages.
- Implement package integrity verification and supply chain security scanning in your build pipeline.
Sources
- GitHub Advisory GHSA-qw4v-qp85-m2fx · GitHub Advisory Database
Cite this entry
"Malicious code in golaaa (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malicious-code-in-golaaa-npm-b1rn6y
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in a.poltoradnev-package-a
The npm package a.poltoradnev-package-a contains malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - activecritical
Malware in @zynkit/probe
Malware discovered in the npm package @zynkit/probe. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
npmCompromised package - containedcritical
Malware in leb128x
The npm package leb128x was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malware in bcs-core
The npm package bcs-core was found to contain malware, resulting in full system compromise for any computer with the package installed or running. All secrets and keys should be rotated immediately from a different computer, and the package should be removed.
npmCompromised package