NeoPass: a Chrome extension that bypasses Iamneo and NPTEL exam restrictions

What NeoPass solves for Iamneo and NPTEL test takers

Exam portals built on Examly and similar platforms lock down the browser during a test. Tab switching is detected, pasting is blocked, and fullscreen screensharing is demanded. NeoPass is a Chrome extension that re-enables those actions and adds an AI assistant inside the same tab, so a student does not have to leave the exam page to look something up. The README frames the audience explicitly: students taking tests on the Iamneo portal, HackerRank, several NPTEL courses (Wildlife Ecology, conservation-geography, forest management) and "other exam portals in chrome browser." The extension also mimics NeoExamShield, the proctoring extension the portal expects, which is the mechanism the repository's description calls a disguise. That is the whole product: it does not teach the material, it removes the friction the portal imposes. Anyone who is not sitting one of those assessments has no reason to install it.

How the extension works: content script, popup, worker

The repository layout is a standard Manifest V3 extension. contentScript.js is injected into exam pages and is where the bypass behaviour lives: intercepting paste events, suppressing visibility and blur signals that portals use to detect tab switches, and holding the fullscreen share stream. popup.html and popup.js render the toolbar UI, including the Settings tab where a free user enters an API key and the Pro tab where a subscriber logs in. worker.js is the background service worker that talks to the AI providers, which keeps the API key out of the page context. devtools.js and the scripts/ directory handle the developer-facing pieces, and data/ holds the question bank, with data/nptel.json as the NPTEL dataset. The AI path is provider-agnostic: the README lists OpenAI, Google Gemini, Anthropic Claude and custom endpoints, selected from a dropdown in Settings. Answers come back through the same content script and are rendered as an overlay or typed into the page. The Pro tier replaces the direct provider call with NeoPass-managed AI, which the README identifies as GPT-5.1, and adds the screenshare modes.

Installing NeoPass from the ZIP and configuring an AI key

The README gives a five-step install and there is no build step. Download the repository ZIP, unpack it, then load the folder as an unpacked extension. The README links the archive for the main branch, so the folder name follows the branch. After loading, the extension icon appears in the toolbar and the Settings tab is where you configure a provider.

# download and unpack the repository
git clone https://github.com/Max-Eee/NeoPass.git
cd NeoPass

In Chrome, open the extensions page with chrome://extensions/, turn on Developer mode in the top right, click Load unpacked and select the NeoPass folder. The README notes the extension should then be listed as installed. Next, click the NeoPass icon, go to Settings, paste an API key for OpenAI, Google Gemini, Anthropic or a custom endpoint, pick the provider from the dropdown and press Test Connection. A successful test is the signal that the key and the network path both work. On the exam page, the documented shortcuts are Alt+A to search answers with AI, Alt+T to autotype an Iamneo coding solution letter by letter, and Ctrl+V to paste when the portal blocks it. The README warns that Alt+Comma, Ctrl+Period and Ctrl+Comma only fire when text is selected first, which is easy to miss on a first run.

NeoPass free vs Pro: where the extension stops working

The free tier is bring-your-own-key and needs no sign-up, which is a reasonable split: you pay your AI provider directly and NeoPass stays a client. The limitation is stated plainly in the README. If a school or organization blocks OpenAI, Google and the other providers at the network level, the extension will not work even with a valid API key, and the README's suggested workarounds are a VPN or the Pro tier, which routes through NeoPass-managed AI and is described as working when AI providers are blocked. That is the real dividing line between the tiers, not the feature list. The Pro tier also gates the three screenshare modes (share only the current tab or window, share a black screen, or freeze a single captured frame), which the README lists under Pro only. Two other constraints matter. The install path is Load unpacked, so the extension is never reviewed or auto-updated by the Chrome Web Store, and the README does not document a rollback or downgrade procedure for a bad release. And the HackerRank shortcut is marked BETA in the README, which is the project's own admission that it is less reliable than the Iamneo path.

How NeoPass differs from a plain AI sidebar extension

A general AI sidebar extension such as ChatGPT's own browser tools or a generic assistant add-on answers questions in a panel. It does not touch the page. NeoPass does the opposite: its value is in the page-level bypass, and the AI is an accessory to it. The paste interception, the tab-switch suppression and the fullscreen share handling are what a portal would otherwise block, and no general assistant extension attempts them. The trade-off runs the other way too. A sidebar extension installs from the Chrome Web Store, updates automatically and is reviewed, while NeoPass is loaded unpacked from a ZIP and its release cadence is visible only in the repository. If you only need an AI assistant and your exam portal does not restrict the browser, NeoPass is the wrong tool and a normal assistant extension is simpler. If the portal does restrict the browser, no general-purpose extension will help, because the restriction is enforced on the page, not in the assistant.

Contributing NPTEL questions and the data/nptel.json format

The NPTEL answer coverage is a dataset, not a model, and the README documents how to extend it. The workflow is manual by design: fork the repository, open an NPTEL assignment page, open developer tools, go to the Console tab, paste the script from nptel.txt and run it. The script extracts the questions and correct answers from the page and prints JSON, which you then merge into data/nptel.json and submit as a pull request. The README's instructions are truncated at that last step, so the exact merge format is not spelled out beyond "update the data/nptel.json file." That is a gap worth noting: a contributor has to infer the schema from the existing file. It also means NPTEL accuracy depends on how current the dataset is, and the repository does not document a refresh schedule for it. For courses not in the dataset, the extension falls back to the AI provider, which is why the free tier still needs a key.

Licence, maintenance and upgrade cost

The repository does not carry a licence file in the top-level entries, and the README does not state terms for the code. That matters more than usual here because the extension is distributed as source that users load unpacked, and the Pro tier is a paid service at neopass.fun/pro. Without a licence, the default position is that no rights are granted beyond what the hosting platform allows, so redistributing a modified build is not something the repository authorizes in writing. Treat that as an open question to resolve with the author rather than an assumption. On maintenance, the last push was on 2026-09-11, and the most recent release is v1.5.5 on the same day, with v1.5.2 in March 2026 and v1.5.1 in January 2026. The release notes file exists but the README does not describe a migration path between versions. Because the install is unpacked, upgrading means replacing the folder contents and reloading the extension in chrome://extensions; there is no automatic update channel, and the README does not document whether settings and the API key survive that replacement.

Editorial conclusion

NeoPass is for students sitting Iamneo, HackerRank or NPTEL assessments who want an AI assistant inside the exam tab and are willing to load an unpacked extension and supply their own API key. It is not for anyone who needs a packaged, reviewed build from the Chrome Web Store, and it is not useful if the exam runs outside Chrome or if the network blocks every AI provider the extension supports. Before relying on it, verify three things: that manifest.json loads without errors under chrome://extensions, that Test Connection succeeds in the Settings tab with your provider, and that the keyboard shortcuts fire on the actual exam page, because the README documents the shortcut list but not which host permissions the content script injects into.

Frequently asked questions

Official sources

1. Issues
2. Max-Eee/NeoPass on GitHub
3. Project website
4. README
5. Releases