Trapdex Subscribe

CampaignsBrowser extension

Trust Wallet Chrome extension 2.68 published with a leaked store API key

Do this now

  1. Make sure no endpoint still runs 2.68, and move funds from wallets used on it to new seed phrases
  2. Treat store-publishing API keys as release credentials and rotate them after any CI or GitHub secret exposure
  3. Block the listed domains

Indicators to check

Look for any of these on your machines or in your logs:

  • extension-idegjidjbpglichdcondbcbdnbeeppgdph

CSVJSONAll 3 indicators

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

  1. Lure

    Automatic update of a trusted official wallet extension; later a fake 'fix' site

    First seen

  2. Artifact

    Malicious code in a bundled JS chunk (4482.js) that exfiltrates seed phrases

  3. Actor

    No source we cite attributes this activity to an actor.

  4. Infrastructure

    • Lookalike metrics domain
    • Phishing 'fix' site

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
extension-idegjidjbpglichdcondbcbdnbeeppgdph
domainapi[.]metrics-trustwallet[.]com
domainfix-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.