# MAL-2026-14076: Malicious code in bcs-mini (npm)


- **Type:** Malicious package
- **Package:** `bcs-mini` (npm)
- **Published:** 14 Aug 2026
- **Also known as:** GHSA-9q3f-qc6p-62mm

## What is MAL-2026-14076?

MAL-2026-14076 is a malicious package in bcs-mini, published on 14 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-14076?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14076 is a malicious package: bcs-mini (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14076/ (Markdown: https://insights.sbomify.com/MAL-2026-14076/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14076

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14076/
Summaries are generated and may contain mistakes; the official description above is the record.