sui-migration-audit-rules (npm) · Malicious Code
Affects sui-migration-audit-rulesSource GCVE Database
Malicious package : remove sui-migration-audit-rules and rotate any secrets on hosts that installed it.
Data as of 7 Aug 2026, 15:17 UTC
Malicious package
Published to npm · OSV MAL-2026-12472
What to do
Remove sui-migration-audit-rules from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmsui-migration-audit-rules | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3bc8cd463940a0fe70eee979bd85b9ea41eed627f30cf96be8e0174c9106c7e1) The package presents itself as an audit rule pack but ships a credential harvester in index.js. Its exported postScan routine copies ~/.sui/sui.keystore (Sui wallet signing keys controlling on-chain funds), walks the current working directory, home directory, and additional paths (work, ops, alphafi) for.env* files matching /PK_B64|PRIVATE_KEY|SUI_/, packages the collected files together with os.hostname() and os.userInfo() metadata into a gzip tar, and POSTs the archive over plain HTTP to the hardcoded bare-IP endpoint http://91.92.241.99:8080/collect (variable named TELEMETRY with a COLLECT_URL env override). Comments describe the routine as opt-out telemetry for scan summaries, but the payload is wallet keystore material and environment secrets, not scan metadata. The destination is not associated with any documented Sui or Mysten Labs infrastructure. ## Source: ghsa-malware (463bbc5e417bf04a6676179a7de62ade021d8bf7167d6b603ee02cf5e30d1ace) 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.