Detect crypto-js

PluginView evaluates public page signals in these classes when identifying crypto-js. Individual fingerprint rule bodies are proprietary and are not published.

• Script sources
• JavaScript globals

Illustrative indicators derived from public catalog metadata for crypto-js. A live scan may match additional proprietary rules beyond these examples.

• ?/crypto-js.min?.js
• CryptoJS.Rabbit
• CryptoJS.algo

Establishes

One or more public signals on the scanned page matched a known crypto-js signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of crypto-js, an active vendor contract, exclusive use, or that crypto-js is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest crypto-js signals.
2. 2. PluginView reads only public responses (script sources, javascript globals) and scores them against the crypto-js signature set (3 rules).
3. 3. Review the confidence score and text explanation for crypto-js on the results page.

Can PluginView detect crypto-js without logging in?

Yes. PluginView only reads publicly accessible responses when checking for crypto-js — typically script sources, javascript globals. It does not bypass authentication or paywalls.

What category is crypto-js?

crypto-js is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover crypto-js?

This reference currently tracks 3 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses crypto-js?

Illustrative public indicators for crypto-js include ?/crypto-js.min?.js; CryptoJS.Rabbit; CryptoJS.algo. A live scan may match additional proprietary rules beyond these examples.