Dormant IoliteLabs Solidity extensions made malicious after eight years
- Taken downas of
- Moderate confidence
- Indicators (6): CSV, JSON
- Seen to
Do this now
- Remove iolitelabs.solidity-* and block the two payload domains
- Hunt for an unsigned 'Chrome updater' MSI or hook DLL installed around 25 Mar 2026
- Flag dormant extensions that suddenly publish new versions
Indicators to check
Look for any of these on your machines or in your logs:
- extension-id
iolitelabs[.]solidity-macos - extension-id
iolitelabs[.]solidity-windows - extension-id
iolitelabs[.]solidity-linux
What happened
Three Solidity extensions first published in 2018 (about 27.5k installs) received a 0.1.8 update. The update hid a dropper inside a modified bundled compression library. On Windows it delivered a fake Chrome-updater MSI with a hook DLL, and on macOS it delivered Node-based binaries. The targets were Solidity and crypto developers.
- VS Code Marketplace
- Windows
- macOS
Attack chain
-
Lure
Long-standing Solidity language-support extensions
First seen
-
Artifact
0.1.8 VSIX with a trojanized bundled pako/index.js and platform droppers (calc.bat, doc.sh)
-
Actor
No source we cite attributes this activity to an actor.
-
Infrastructure
- Payload domains for the Windows and macOS stages
Last seen
Timeline
- First seen
- StepSecurity reports
- Microsoft vsmarketplace reports
- Last seen
- Status checked: Taken down
Related campaigns
| Type | Value | Copy |
|---|---|---|
| extension-id | iolitelabs[.]solidity-macos | |
| extension-id | iolitelabs[.]solidity-windows | |
| extension-id | iolitelabs[.]solidity-linux | |
| domain | rraghh[.]com | |
| domain | oortt[.]com | |
| sha256 | fcd398abc51fd16e8bc93ef8d88a23d7dec28081b6dfce4b933020322a610508 |
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
- Microsoft's RemovedPackages.md lists all three variants (macOS, Windows and Linux) as removed for malware on 28 Mar 2026 (checked 9 Nov 2026).
Corrections
No corrections.
See the corrections policy. Spotted an error? Tell us.