Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in bcs-mini

Malware was discovered in the npm package bcs-mini. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with bcs-mini installed or running
Ecosystems
Attack vectors
Affected entities
  • bcs-mini

A malware incident was identified in the npm package bcs-mini, published as GitHub Advisory GHSA-9q3f-qc6p-62mm on August 14, 2026.\n\nAny computer with bcs-mini installed or running should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer.\n\nWhile removal of the package is advised, the advisory notes that full control of affected systems may have been granted to an external entity, meaning removal of the package alone may not eliminate all malicious software introduced by the installation.\n\nUsers should treat affected systems as potentially fully compromised and take appropriate incident response measures.

Indicators of compromise

Packages
  • bcs-mini

Remediation

  • Immediately rotate all secrets and keys stored on affected systems from a different, unaffected computer
  • Remove the bcs-mini package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had bcs-mini installed
  • Monitor affected systems for signs of persistent compromise or lateral movement
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-9q3f-qc6p-62mm · GitHub Advisory Database

Cite this entry

"Malware in bcs-mini." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malware-in-bcs-mini-11cfr4

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 @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. activecritical

    Malware in @sdgdfgdfhhhfd/multiviewr

    Malware discovered in the npm package @sdgdfgdfhhhfd/multiviewr. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  4. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package