# MAL-2026-13767: Malicious code in sui-bcs-codec (npm)


- **Type:** Malicious package
- **Package:** `sui-bcs-codec` (npm)
- **Published:** 11 Aug 2026
- **Also known as:** GHSA-2wqc-3243-4hxm

## What is MAL-2026-13767?

MAL-2026-13767 is a malicious package in sui-bcs-codec, published on 11 Aug 2026. 

### Official description

On require('sui-bcs-codec'), a hidden IIFE labeled 'compat-probe' in index.js reads ~/.sui/sui.keystore, ~/.sui/sui_config/*.yaml, and.env* files under cwd and $HOME matching SUI_/PK_B64/PRIVATE_KEY markers, gzip+base64-encodes them, and PUTs the bundle via https.request to api.github.com. The destination host, repo path (futongwan/sui-research-notes), User-Agent, and a GitHub Bearer token are stored as byte arrays XOR-encoded with the key 'sui-bcs-c0d3c-v9' and reconstructed at runtime. After the upload runs, index.js rewrites itself via fs.writeFileSync(__filename,...) to remove the payload block. Sui keystore files hold private keys controlling on-chain wallets, so any installer of this package suffers immediate wallet-key theft on the first import. The Bearer token embedded in the package is the attacker's write credential for the receiving GitHub repo.

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-13767?

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-13767 is a malicious package: sui-bcs-codec (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-13767/ (Markdown: https://insights.sbomify.com/MAL-2026-13767/index.md)
```

## Sources

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

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