Skip to content
GDPR compliant. Hosted in DE.
14-day free trial →
Module · XICTRAQ

Script integrity & skimming protection — web-skimming watch

Monitors the SHA-256 hash of every external third-party script and alerts on unnoticed changes — a typical web-skimming signal. Also watched: new external form targets on checkout paths.

from Business plan
No credit card Servers in Germany 3 EU probe nodes 14-day pro trial GDPR compliant
Live status
Script integrity & skimming protection — web-skimming watch
ACTIVE
Hash baseline per script
During the scan the SHA-256 hash of every external third-party script is learned and stored with host, size in bytes and context. This baseline is the reference for all subsequent checks.
Continuous integrity check
A cron re-fetches the monitored scripts regularly and compares their hash against the baseline. This surfaces even silent changes that would otherwise go unnoticed in day-to-day operations.
Skimming signal as alert
An unnoticed hash change is a typical web-skimming pattern. XICTRAQ then creates a drift entry and alerts via your channels — exactly once per drift, until you acknowledge it.
Checkout & form integrity
External form targets are captured as well. If a new, foreign form target appears on a checkout path, this is an indication of a possible payment-data leak.
Last check just now
What it does

Embedded third-party scripts are a popular entry point for web skimming: attackers tamper with a seemingly harmless script that loads on many pages and siphon off payment or form data directly in the browser. Such manipulations often go unnoticed for weeks. XICTRAQ learns the hash of every external script as a baseline during the scan and checks it continuously. If a script changes unnoticed -- or a new external form target appears on a checkout path -- you receive an alert and can review, confirm or end the monitoring.

Script integrity & skimming protection — web-skimming watch features

Hash baseline per script

During the scan the SHA-256 hash of every external third-party script is learned and stored with host, size in bytes and context. This baseline is the reference for all subsequent checks.

01 / 06

Continuous integrity check

A cron re-fetches the monitored scripts regularly and compares their hash against the baseline. This surfaces even silent changes that would otherwise go unnoticed in day-to-day operations.

02 / 06

Skimming signal as alert

An unnoticed hash change is a typical web-skimming pattern. XICTRAQ then creates a drift entry and alerts via your channels — exactly once per drift, until you acknowledge it.

03 / 06

Checkout & form integrity

External form targets are captured as well. If a new, foreign form target appears on a checkout path, this is an indication of a possible payment-data leak.

04 / 06

Acknowledge & dismiss workflow

Legitimate changes are confirmed via Acknowledge — the current hash becomes the new baseline. With Dismiss you end monitoring of an entry entirely.

05 / 06

Overview of open drifts

A clear status per website shows how many scripts are monitored and how many drifts are open. Each entry names host, shortened hash, context and timestamps.

06 / 06
Process

How it works

1

Run a scan on your website

During the on-demand scan, XICTRAQ inventories all external third-party scripts and external form targets and learns the SHA-256 hash as a baseline for each monitored script.

2

Let it check continuously

A cron re-fetches the monitored scripts regularly and compares the hashes. When needed, you can trigger an immediate re-check at any time via “rescan”.

3

React to drift

On an unnoticed change you receive an alert. Confirm a legitimate change via Acknowledge as the new baseline, or end monitoring of the entry via Dismiss.

Skimming protection

From learned hash to drift alert

The SHA-256 hash of every external third-party script is learned as a baseline and checked continuously. An unnoticed change is treated as a possible web-skimming signal — and is alerted exactly once.

1Baseline learnedduring scancheckout.example/pay.jssha256: a1f9…24.8 KB · context: scriptform target on checkoutCron checks hasha1f9 ≠ c4e2script changed unnoticedDrift alertpossible skimming signalexactly once per driftYour responseAcknowledgeconfirm legitimate changecurrent hash becomes new baselinebaseline := c4e2…Dismissend monitoring of the entryno further check, no alertpermanent for this entryIndication based on script integrity — not a conclusive security proof. Available from the Business plan.
Step 1

Learn the baseline

During the scan the SHA-256 hash of every external third-party script is captured and stored as a baseline — together with host, size and context (script or form target).

Step 2

Check hashes continuously

A cron re-fetches the monitored scripts and compares their hash against the baseline. As long as everything stays equal, nothing happens.

Step 3

Alert on drift

If a script changes unnoticed, this is treated as a possible web-skimming signal: you receive exactly one alert per drift — no repeated noise.

Step 4

Acknowledge or end

With Acknowledge you confirm a legitimate change as the new baseline. With Dismiss you end monitoring of an entry entirely.

Drift detection is based on hash comparisons of embedded third-party scripts and external form targets — an indication, not a conclusive security proof. Available from the Business plan.

FAQ

Frequently Asked Questions

What exactly is monitored?
During the scan, XICTRAQ captures every external third-party script your pages embed and computes the SHA-256 hash over the delivered script content. This hash is stored as a baseline together with host, size in bytes and context. External form targets are captured as well, with special attention to checkout paths.
How does XICTRAQ detect web skimming?
Web skimming (as a generic term often called a “Magecart attack”) tampers with an embedded script to siphon off payment or form data directly in the browser. Such tampering changes the script content — and thus the hash. If the continuously checked hash deviates from the learned baseline without you having confirmed the change, XICTRAQ treats this as a possible skimming signal and alerts. This is an indication based on script integrity, not a conclusive security proof.
What do Acknowledge and Dismiss mean?
Scripts get updated legitimately — for example when an embedded service ships an update. In that case you confirm the change via Acknowledge: the current hash becomes the new baseline and the drift is considered resolved. If you no longer want to monitor a script at all, you end monitoring of the entry via Dismiss.
Will I be alerted again on every change?
No. A drift is alerted only once — until you confirm it via Acknowledge or end it via Dismiss. This keeps it to one clear signal instead of repeated noise, even though the cron keeps seeing the changed script on every run.
Why are checkout paths especially important?
On checkout and form pages, payment and contact data are entered. That is exactly where a tampered script or a new, foreign form target is particularly critical, because sensitive data can leak through it. XICTRAQ therefore flags entries with form context and specifically watches for new external form targets on detected checkout paths.
Which plan includes script integrity?
Script integrity and skimming monitoring is available from the Business plan. It complements the security scan and the visual diff with content integrity signals for embedded third-party scripts and form targets.
Start in 60 seconds

Let XICTRAQ watch your website.

Permanent free plan available. No credit card, no installation, no hidden fees.