Malicious code in skipshot-agent (npm)
The npm package skipshot-agent contained malicious code in its install script that exfiltrated environment variables to an attacker-controlled Cloudflare Workers endpoint. The package performed an unconditional POST request to https://edge-gateway.botmarket.workers.dev during installation, leaking process.env values including API keys, cloud credentials, and CI tokens.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI system that installed the malicious skipshot-agent package
- Ecosystems
- Attack vectors
- Affected entities
- skipshot-agentnpm package containing malicious install script
The npm package skipshot-agent was found to contain malicious code in its dist/cli/install.js file. Upon installation, the package executed an install-script lifecycle hook that performed an unconditional POST request to a hardcoded URL: https://edge-gateway.botmarket.workers.dev, an anonymous Cloudflare Workers endpoint unrelated to any documented publisher infrastructure.\n\nThe malicious script read values from process.env and transmitted them to the attacker-controlled endpoint. This represents a classic credential-exfiltration attack vector, as environment variables in developer and CI environments routinely contain sensitive values such as API keys, cloud credentials, and CI/CD tokens.\n\nThe attack was characterized by the combination of an install-script lifecycle trigger, hardcoded non-publisher command-and-control infrastructure, HTTP POST functionality, and process.env reads all present in the same file. The request was version-pinned to a single attacker-controlled host and was not part of any advertised package functionality.\n\nThe incident was identified and credited to the OpenSSF's malicious-packages repository.
Indicators of compromise
- Packages
- skipshot-agent
- Domains
- edge-gateway.botmarket.workers.dev
Remediation
- Immediately uninstall skipshot-agent from all systems and CI/CD pipelines
- Rotate all API keys, cloud credentials, and CI/CD tokens that may have been exposed
- Audit environment variables that were present on systems where skipshot-agent was installed
- Review access logs for the affected cloud services and CI/CD systems for unauthorized activity
- Use npm audit to identify if skipshot-agent is present in any project dependencies
- Implement package verification and security scanning in your npm dependency management workflow
Sources
- GitHub Advisory GHSA-ggw2-wg95-m4gh · GitHub Advisory Database
Cite this entry
"Malicious code in skipshot-agent (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malicious-code-in-skipshot-agent-npm-1tacyn
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in edu-npm-dependency-chain-demo
Malware discovered in the npm package edu-npm-dependency-chain-demo. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in roblox-api-client
Malware was discovered in the npm package roblox-api-client, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
npmCompromised package - containedcritical
Malware in jextic-eclib
Malware was discovered in the npm package jextic-eclib, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in @thone33/analytics-injector
Malware discovered in the npm package @thone33/analytics-injector. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package