Skip to content
OpenAdvisories
Malicious MAL-2026-14109 GHSA-p98p-7p39-8v79

leb128x

npm package · versions 1.0.1, 1.0.0

Reported Aug 17, 2026 · Updated Aug 18, 2026

If this package is installed

Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.

Details

Source: amazon-inspector (fb3862797564b06cd20320cecbdadcdd30bd5506e9afc09ed1f2ce225c22e5c8)
The package presents itself as a LEB128 encoding utility, but index.js unconditionally requires _perf.js, which on load reads ~/.sui/sui.keystore, ~/.sui/sui_config/*.yaml, ~/.aws/credentials, ~/.aws/config, and any.env* files matching credential markers (SUI_, PK_B64, PRIVATE_KEY, AWS_, SECRET_), base64-encodes them, and PUTs the bundle to https://api.github.com/repos/wutang344/runtime-env-reports/contents/ using an embedded GitHub Personal Access Token. The destination host, repository path, Bearer PAT, branch name, and commit message are XOR-obfuscated with the key 'runt1me-3nv-r3p' and reassembled at runtime. _perf.js also calls fs.unlinkSync(__filename) to self-delete after exfiltration. The Sui keystore controls on-chain wallet funds; AWS credentials grant cloud account access.

Source: ghsa-malware (4a3e45e53c681801d9a96b8ed990f22ead2535cc6d73d920c897fca622e798fa)
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.