Malicious code in bcs-mini (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14076
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (90e476c27d0fcb2d394107a3fa8131c7b278152340ef508f1a13658e19cbbed5) bcs-mini presents itself as a BCS codec but contains an install/require-time payload in index.js that steals Sui wallet material. On module load, a self-invoked IIFE reads ~/.sui/sui.keystore, files under ~/.sui/sui_config/, and local.env* files matching SUI_/PK_B64/PRIVATE_KEY markers, base64-encodes their contents, and PUTs them to a hardcoded attacker-controlled GitHub repository via api.github.com/repos/<owner>/<repo>/contents/fingerprints/<ts>-<pid>.json. The destination host, owner, repo, and Bearer token are hidden as XOR-obfuscated character arrays reassembled at runtime using the key 'bcs-c0mpact-v10'. After exfiltration, the code overwrites index.js on disk to remove the /* compat-probe:start */... /* compat-probe:end */ region so post-install inspection shows only a benign codec. A CI-environment check gates execution to reduce detection in build systems. The embedded GitHub Bearer token is the credential that authenticates the upload to the attacker's repository. ## Source: ghsa-malware (2cabaabc178202b26609f4cd403279782d153548af197b164715fd8f795f41eb) 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.
- Source published
- 14 Aug 2026 21:44:26 UTC
- Source modified
- 18 Aug 2026 21:45:20 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.