Trust Wallet Chrome extension 2.68 published with a leaked store API key
- Taken downas of
- Moderate confidence
- Indicators (3): CSV, JSON
- Seen to
Do this now
- Make sure no endpoint still runs 2.68, and move funds from wallets used on it to new seed phrases
- Treat store-publishing API keys as release credentials and rotate them after any CI or GitHub secret exposure
- Block the listed domains
Indicators to check
Look for any of these on your machines or in your logs:
- extension-id
egjidjbpglichdcondbcbdnbeeppgdph
What happened
Developer secrets exposed in the Shai-Hulud 2.0 npm worm included a Chrome Web Store API key. Attackers used it to publish version 2.68.0 of the official Trust Wallet extension with code that sent seed phrases to a lookalike domain. Trust Wallet reports about 2,520 wallets drained of about USD 8.5M between 24 and 26 Dec. Version 2.69 removed the code, and a follow-up phishing site targeted users looking for a fix.
- Chrome
Attack chain
-
Lure
Automatic update of a trusted official wallet extension; later a fake 'fix' site
First seen
-
Artifact
Malicious code in a bundled JS chunk (4482.js) that exfiltrates seed phrases
-
Actor
No source we cite attributes this activity to an actor.
-
Infrastructure
- Lookalike metrics domain
- Phishing 'fix' site
Last seen
Timeline
- First seen
- BleepingComputer reports
- Trust Wallet reports
- Last seen
- Status checked: Taken down
Related campaigns
| Type | Value | Copy |
|---|---|---|
| extension-id | egjidjbpglichdcondbcbdnbeeppgdph | |
| domain | api[.]metrics-trustwallet[.]com | |
| domain | fix-trustwallet[.]com |
Confidence: Moderate
Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.
Sources
Notes
- Loss figures differ (about USD 7M early, USD 8.5M later). Also fits publisher-pipeline; filed here once. Linked to shai-hulud-2-npm-worm.
Corrections
No corrections.
See the corrections policy. Spotted an error? Tell us.