Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in bcore-bravo-eslint-config (npm)

The npm package bcore-bravo-eslint-config contained malicious code that, when required, downloads and executes platform-specific native binaries from Cloudflare Workers mirrors and a fallback domain. The package masquerades as an ESLint configuration module but performs arbitrary code execution at import time.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any developer or CI/CD system that installed bcore-bravo-eslint-config would execute arbitrary native code at require-time, potentially compromising build environments and downstream artifacts.
Ecosystems
Attack vectors
Affected entities
  • bcore-bravo-eslint-confignpm package containing malicious dropper code

The npm package bcore-bravo-eslint-config was published with embedded malicious code designed to execute arbitrary native binaries. When the package is imported via require(), it triggers a bootstrap sequence that downloads platform-specific executables (Linux x64, macOS ARM64, macOS x86, Windows) from rotating Cloudflare Workers subdomains and a dl.well1.site fallback domain.\n\nThe attack uses obfuscation techniques to hide malicious intent: destination hostnames and dangerous API calls are assembled through string-splitting and dynamic property lookup (e.g., require(\"child_\"+\"process\"), os[\"plat\"+\"form\"], fs[\"chmod\"+\"Sync\"]). The fetched binaries are base64-decoded, written to a staging path, marked executable, and executed via child_process.\n\nThe package exports a minimal 24-line ConfigLoader API unrelated to the actual payload, making it appear legitimate to casual inspection. The name suggests a typosquatting variant of a legitimate ESLint configuration package. Any developer or CI/CD pipeline that installed this package would execute arbitrary code at require-time, potentially compromising build environments and downstream software artifacts.\n\nThe incident was detected and reported via Amazon Inspector, and the package has been removed from npm.

Indicators of compromise

Packages
  • bcore-bravo-eslint-config
Domains
  • dl.well1.site

Remediation

  • Immediately remove bcore-bravo-eslint-config from all package.json files and lock files
  • Audit npm install logs and CI/CD build logs for any execution of this package
  • Assume any build environment that installed this package is compromised; rotate credentials and secrets used in those environments
  • Scan systems that ran builds with this package for unexpected network connections to Cloudflare Workers subdomains or dl.well1.site
  • Review and re-sign any artifacts built with this package present in the dependency tree
  • Use npm audit and supply chain security tools to detect similar typosquatting and dropper patterns

Sources

  1. GitHub Advisory GHSA-rp5f-362v-pw3h · GitHub Advisory Database

Cite this entry

"Malicious code in bcore-bravo-eslint-config (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-bcore-bravo-eslint-config-npm-1yblwg

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting
  2. resolvedcritical

    Malicious code in depcruise-wrap-stream-in-html (npm)

    depcruise-wrap-stream-in-html@99.9.1 is a malicious npm package that mimics an internal helper of dependency-cruiser. It is a hollow package that downloads and executes arbitrary code from a Google Cloud Storage bucket during installation.

    npmCompromised packageDependency confusionTyposquatting
  3. resolvedcritical

    Malicious code in @finaxis/common-js (npm)

    The npm package @finaxis/common-js was published with a README and keywords copied from lodash v4.18.1, but contained a heavily obfuscated Xelis (XEL) proof-of-work cryptominer instead of lodash functionality. Consumers installing this package would unknowingly run a covert CPU/GPU miner on their systems.

    npmCompromised packageTyposquatting
  4. containedcritical

    Malicious code in axios-fast (npm)

    axios-fast@1.0.1 on npm contains malicious code that exfiltrates environment variables (including AWS credentials, NPM tokens, and GitHub tokens) to an attacker-controlled webhook during package installation. The package typosquats the legitimate axios HTTP client library.

    npmCompromised packageTyposquatting