browser extension

The Nano Defender and Nano Adblocker Supply Chain Attack

Updated 5 Oct 2026 · Incident date 15 Oct 2020

Nano Defender 15.0.0.206 and Nano Adblocker began running remote code after the original developer sold the project, in October 2020.

The new owners added a file named connect.js. It called code from remote servers and sent browser activity to them.

What happened

The original developer, jspenguin2017, sold the project in early October 2020. The new owners then shipped an update that acted against its users.

  • Born City reports that the buyers were developers in Turkey.
  • Nano Defender 15.0.0.206 added connect.js, which loaded code from remote servers.
  • It sent user activity and browser data to https://def.dev-nano.com/.
  • Lowyat reports that the code liked large numbers of Instagram posts and uploaded authentication cookies.
  • Users got the new version through normal automatic updates. Google removed the extensions from the Chrome Web Store.

Reports tie the extensions to unwanted activity on users' Instagram accounts.

Affected versions

  • Nano Defender 15.0.0.206 and the matching Nano Adblocker build, in Chromium-based browsers such as Chrome and Edge. This applies to installs from the Chrome Web Store.
  • Born City also lists User-Agent Switcher, Nano Contrib Filter - Placeholder Buster, Nano Defender Integration and the Nano filters extensions.
  • The sources disagree on other browsers. Check each browser you use.

Indicators of compromise

  • Script file: connect.js inside the extension.
  • Server: def.dev-nano.com.
  • Extension version: Nano Defender 15.0.0.206.
  • Likes on your Instagram account that you did not make.

How to check

Open chrome://extensions and check the version of Nano Defender. You can also search the profile folder for the server name. On macOS:

grep -rl "dev-nano.com" ~/Library/Application\ Support/Google/Chrome/*/Extensions 2>/dev/null

A hit means that an installed extension contains the server name.

What to do now

  1. Uninstall every Nano extension from each Chromium browser.
  2. Sign out of all websites. This ends sessions that a stolen cookie can use.
  3. Change your passwords, starting with social accounts such as Instagram.
  4. Look at account activity for likes, posts or logins that you did not make.

Frequently asked questions

Are other browsers affected?

The sources disagree. Lowyat states that the Firefox version and the Edge-store version were not affected.

Who inspected the code?

The uBlock Origin developer, Raymond Hill. Nano Adblocker was based on uBlock Origin code.

Sources

  1. borncity.com/win/2020/10/22/datenklau-browser-extension-nano-adblocker-defender-co-entfernen/
  2. lowyat.net/2020/224264/chromium-versions-nano-adblocker-malware/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library