Detect Crypto-Loot

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

• Script sources
• JavaScript globals

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

• crypto-loot.com/lib/
• webmine.pro/
• cryptoloot.pro/
• crlt.js
• CRLT.CONFIG.ASMJS_NAME
• CryptoLoot

Establishes

One or more public signals on the scanned page matched a known Crypto-Loot signature (6 rules) at the time of the scan.

Does not establish

A sitewide install of Crypto-Loot, an active vendor contract, exclusive use, or that Crypto-Loot 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-Loot signals.
2. 2. PluginView reads only public responses (script sources, javascript globals) and scores them against the Crypto-Loot signature set (6 rules).
3. 3. Review the confidence score and text explanation for Crypto-Loot on the results page.

Can PluginView detect Crypto-Loot without logging in?

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

What category is Crypto-Loot?

Crypto-Loot is classified under Cryptominers in the PluginView directory.

How many fingerprint rules cover Crypto-Loot?

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

What public signals suggest a site uses Crypto-Loot?

Illustrative public indicators for Crypto-Loot include crypto-loot.com/lib/; webmine.pro/; cryptoloot.pro/. A live scan may match additional proprietary rules beyond these examples.