🛠️ Tampering Antifraud Requests using Burp Suite 🛠️

[Nitroomx]

Excellent

 

[kingfun6699]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Việc giải mã mã hóa cần có kỹ năng, nhưng không phải là khoa học tên lửa. Bạn chỉ cần đảo ngược kỹ thuật để tìm ra cách JS tạo ra tải trọng. Đối với những ai có IQ dưới 70, hãy tham khảo AI. Và nếu bạn cảm thấy mình thông minh khi nghĩ rằng chỉ có Base64 cho Riskified (mặc dù nhiều người trong số họ chỉ sử dụng mã hóa Base64), thì không phải vậy:

Nhưng bạn biết tôi mà, tôi yêu tất cả các bạn nên đối với bản demo này, tôi đã phát triển một công cụ giúp giải mã dấu vân tay từ các giải pháp chống phát hiện phổ biến. Đối với bản demo này, tôi đã bật Riskified nhưng tôi sẽ sớm thêm hầu hết các nhà cung cấp chống gian lận.

​

[URL mở rộng="true"]https://binx.cc/tools/antifraud-deobfuscate[/URL]

Vì vậy, để mọi việc dễ dàng hơn, hãy đến công cụ giải mã chống gian lận trong BinX và chọn Riskified , sau đó dán dữ liệu đã chặn của chúng tôi.

Sau khi giải mã, dữ liệu dấu vân tay của bạn sẽ trông giống như một cuốn sách mở.
[MÃ SỐ]
{
"vĩ độ": 37.7749,
"múi giờ": 240,
"dấu thời gian": "1689452187394",
"cart_id": "7629384105",
"shop_id": "cf.bstatic.com",
"người giới thiệu": "https://secure.booking.com/",
"href": "https://cf.bstatic.com/static/tag_c...a077563c1795a773c91150dd19adefe98d13fd65.html",
"riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
"color_depth": 24,
"page_id": "9xzp4r",
"cửa hàng": "www.booking.com",
"hardware_concurrency": 8,
"has_touch": đúng,
"lịch sử_chiều dài": 7,
"document_title": "Đặt phòng.com",
"console_error": "console.memory không được xác định",
"battery_error": "Lỗi getBattery()",
"initial_cookie_state_0": "https",
"initial_cookie_state_1": "liên tục",
"trình duyệt": {
"productsub": "20030107",
"is_opr": đúng,
"is_firefox": sai,
"ev_len": 42
},
"hệ điều hành": {
"cpu": "Windows NT 10.0",
"nền tảng": "Win32"
},
"webgl": {
"nhà cung cấp": "Google Inc.",
"trình kết xuất": "GÓC (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
},
"nghị quyết": {
"dpr": 1,5,
"màn hình": 1080,
"màn hình": 1920,
"có sẵn": 1040,
"có sẵn": 1920,
"bên trong": 900,
"bên trong": 1600,
"bên ngoài": 1040,
"bên ngoài": 1920
},
"date_string": "Thứ sáu, ngày 25 tháng 3 năm 2025 14:23:07 GMT-0400 (Giờ ban ngày miền Đông)",
"quốc tế": {
"locale": "en-GB",
"num_sys": "vĩ độ",
"cal": "gregory",
"tz": "Mỹ/New_York"
},
"downlink_error": "navigator.connection không được xác định",
"nav_plu": "Trình cắm PDF của Chrome, Trình xem PDF của Chrome, Máy khách gốc",
"nav_lang": "vi-GB",
"dữ liệu ngôn ngữ trang": {
"page_language": "vi",
"has_translation": đúng
},
"ẩn danh": {
"safari": đúng,
"chrome_quota": 120,
"service_worker_undefined": sai,
"is_brave": đúng
}
}
[/MÃ SỐ]



Sau đó, bạn có thể thực hiện các chỉnh sửa chiến lược để tăng cường các yếu tố tin cậy và phù hợp với hồ sơ mục tiêu của mình:

* Văn bản ẩn: không thể trích dẫn. *


Sau khi thực hiện thay đổi, hãy làm tối nghĩa lại và thay thế dữ liệu trong bảng điều khiển chặn của bạn và CHUYỂN TIẾP yêu cầu.

Quá trình này liên kết dấu vân tay giả của bạn với cookie của bạn. Hệ thống nghĩ rằng bạn chỉ là một khách hàng hợp pháp khác thay vì là kẻ lừa đảo kỹ thuật số thực sự.

Phần kết luận

Thao túng các hệ thống chống gian lận bằng Burp Suite giống như có một bộ ngụy trang kỹ thuật số. Bạn không chỉ thay đổi diện mạo của mình – bạn đang thay đổi những gì camera an ninh nhìn thấy. Bằng cách đặt Burp giữa trình duyệt của bạn và các hệ thống này, bạn có thể cung cấp cho chúng bất kỳ dấu vân tay nào bạn muốn, thậm chí không cần sử dụng antidetect.

Thành công phụ thuộc vào việc hiểu chính xác những gì các hệ thống này thu thập và cách chúng diễn giải chúng. Phân tích nhật ký Burp của bạn để nghiên cứu các yêu cầu chống gian lận trước khi can thiệp vào chúng. Tìm kiếm các mẫu trong dữ liệu JSON. Bạn càng hiểu rõ những gì họ đang kiểm tra thì bạn càng có thể thao tác chính xác hơn.

Hãy nhớ: sự lừa dối hiệu quả trên mạng không phải là sự vô hình – mà là trông thật bình thường đến nỗi họ không bao giờ nghĩ đến việc phải nhìn lần thứ hai.

Hãy nhớ rằng chúng ta mới chỉ khai thác được bề nổi những gì Burp Suite có thể làm. Công cụ khủng này có hàng chục mô-đun và hàng trăm tính năng mà tôi thậm chí còn chưa đề cập đến - từ quét tự động đến tìm lỗ hổng SQLi đến fuzzing điểm cuối. Đây là một công cụ phức tạp, mang lại phần thưởng cho những ai đầu tư thời gian để thành thạo. Tôi sẽ đề cập đến các kỹ thuật nâng cao hơn trong các hướng dẫn sau.

Hẹn gặp lại sớm. d0ctrine ra mắt.

hy

 

[skibidigyat]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Deobfuscating the code takes skill, but its not rocket science. You just need to reverse engineer how the JS created the payload. For those of you whose IQ is below 70 just consult an AI. And if you're feeling like a smartass thinking it's just Base64 for Riskified (though a lot of them just use Base64 encode), it isn't:

But you know me, I love all of you so for this demo I've developed a tool to help deobfuscate fingerprints from popular antidetect solutions. For this demonstration, Ive enabled Riskified but I'll be adding most anti-fraud providers soon.

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

So to make things easier, head to the anti-fraud deobfuscation tool in BinX and select Riskified, and paste our intercepted payload.

After deobfuscation your fingerprint data appears like an open book.

{
  "lat": 37.7749,
  "timezone": 240,
  "timestamp": "1689452187394",
  "cart_id": "7629384105",
  "shop_id": "cf.bstatic.com",
  "referrer": "https://secure.booking.com/",
  "href": "https://cf.bstatic.com/static/tag_container/tag_container/a077563c1795a773c91150dd19adefe98d13fd65.html",
  "riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
  "color_depth": 24,
  "page_id": "9xzp4r",
  "shop": "www.booking.com",
  "hardware_concurrency": 8,
  "has_touch": true,
  "history_length": 7,
  "document_title": "Booking.com",
  "console_error": "console.memory is undefined",
  "battery_error": "Error getBattery()",
  "initial_cookie_state_0": "https",
  "initial_cookie_state_1": "persistent",
  "browser": {
    "productsub": "20030107",
    "is_opr": true,
    "is_firefox": false,
    "ev_len": 42
  },
  "os": {
    "cpu": "Windows NT 10.0",
    "platform": "Win32"
  },
  "webgl": {
    "vendor": "Google Inc.",
    "renderer": "ANGLE (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
  },
  "resolution": {
    "dpr": 1.5,
    "screenh": 1080,
    "screenw": 1920,
    "availh": 1040,
    "availw": 1920,
    "innerh": 900,
    "innerw": 1600,
    "outerh": 1040,
    "outerw": 1920
  },
  "date_string": "Fri Mar 25 2025 14:23:07 GMT-0400 (Eastern Daylight Time)",
  "intl": {
    "locale": "en-GB",
    "num_sys": "latn",
    "cal": "gregory",
    "tz": "America/New_York"
  },
  "downlink_error": "navigator.connection is undefined",
  "nav_plu": "Chrome PDF Plugin,Chrome PDF Viewer,Native Client",
  "nav_lang": "en-GB",
  "page_language_data": {
    "page_language": "en",
    "has_translation": true
  },
  "incognito": {
    "safari": true,
    "chrome_quota": 120,
    "service_worker_undefined": false,
    "is_brave": true
  }
}

You can then make strategic edits to boost trust factors and align with your target profile:

* Hidden text: cannot be quoted. *


Once you've made your changes, obfuscate that shit back and replace the payload in your interception dashboard and FORWARD the request.

This process links your fabricated fingerprint to your cookie. The system thinks youre just another legitimate customer instead of the digital con artist you truly are.

Conclusion

Manipulating antifraud systems with Burp Suite is like having a digital disguise kit. You're not just changing how you look – youre altering what the security cameras see. By positioning Burp between your browser and these systems you can feed them whatever fingerprint you want, without even using an antidetect.

Success depends on understanding exactly what these systems collect and how they interpret it. Analyze your Burp logs to study the antifraud requests before messing with them. Look for patterns in the JSON data. The more you understand what they're checking the more precisely you can manipulate it.

Remember: effective digital deception isnt about invisibility – it's about looking so normal they never think to look twice.

Keep in mind we hae barely scratched the surface of what Burp Suite can do. This beast of a tool has dozens of modules and hundreds of features I haven't even touched on - from automated scanning to finding SQLi vulnerabilities to fuzzing endpoints. Its a complex tool that rewards those who invest time mastering it. I'll be covering more advanced techniques in future guides.

See you soon. d0ctrine out.

tsdvrgvgdfsh

 

[lucidity]

Thanks for the guide, this'll be of great help

 

[wh1t3lies]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Deobfuscating the code takes skill, but its not rocket science. You just need to reverse engineer how the JS created the payload. For those of you whose IQ is below 70 just consult an AI. And if you're feeling like a smartass thinking it's just Base64 for Riskified (though a lot of them just use Base64 encode), it isn't:

But you know me, I love all of you so for this demo I've developed a tool to help deobfuscate fingerprints from popular antidetect solutions. For this demonstration, Ive enabled Riskified but I'll be adding most anti-fraud providers soon.

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

So to make things easier, head to the anti-fraud deobfuscation tool in BinX and select Riskified, and paste our intercepted payload.

After deobfuscation your fingerprint data appears like an open book.

{
  "lat": 37.7749,
  "timezone": 240,
  "timestamp": "1689452187394",
  "cart_id": "7629384105",
  "shop_id": "cf.bstatic.com",
  "referrer": "https://secure.booking.com/",
  "href": "https://cf.bstatic.com/static/tag_container/tag_container/a077563c1795a773c91150dd19adefe98d13fd65.html",
  "riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
  "color_depth": 24,
  "page_id": "9xzp4r",
  "shop": "www.booking.com",
  "hardware_concurrency": 8,
  "has_touch": true,
  "history_length": 7,
  "document_title": "Booking.com",
  "console_error": "console.memory is undefined",
  "battery_error": "Error getBattery()",
  "initial_cookie_state_0": "https",
  "initial_cookie_state_1": "persistent",
  "browser": {
    "productsub": "20030107",
    "is_opr": true,
    "is_firefox": false,
    "ev_len": 42
  },
  "os": {
    "cpu": "Windows NT 10.0",
    "platform": "Win32"
  },
  "webgl": {
    "vendor": "Google Inc.",
    "renderer": "ANGLE (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
  },
  "resolution": {
    "dpr": 1.5,
    "screenh": 1080,
    "screenw": 1920,
    "availh": 1040,
    "availw": 1920,
    "innerh": 900,
    "innerw": 1600,
    "outerh": 1040,
    "outerw": 1920
  },
  "date_string": "Fri Mar 25 2025 14:23:07 GMT-0400 (Eastern Daylight Time)",
  "intl": {
    "locale": "en-GB",
    "num_sys": "latn",
    "cal": "gregory",
    "tz": "America/New_York"
  },
  "downlink_error": "navigator.connection is undefined",
  "nav_plu": "Chrome PDF Plugin,Chrome PDF Viewer,Native Client",
  "nav_lang": "en-GB",
  "page_language_data": {
    "page_language": "en",
    "has_translation": true
  },
  "incognito": {
    "safari": true,
    "chrome_quota": 120,
    "service_worker_undefined": false,
    "is_brave": true
  }
}

You can then make strategic edits to boost trust factors and align with your target profile:

* Hidden text: cannot be quoted. *


Once you've made your changes, obfuscate that shit back and replace the payload in your interception dashboard and FORWARD the request.

This process links your fabricated fingerprint to your cookie. The system thinks youre just another legitimate customer instead of the digital con artist you truly are.

Conclusion

Manipulating antifraud systems with Burp Suite is like having a digital disguise kit. You're not just changing how you look – youre altering what the security cameras see. By positioning Burp between your browser and these systems you can feed them whatever fingerprint you want, without even using an antidetect.

Success depends on understanding exactly what these systems collect and how they interpret it. Analyze your Burp logs to study the antifraud requests before messing with them. Look for patterns in the JSON data. The more you understand what they're checking the more precisely you can manipulate it.

Remember: effective digital deception isnt about invisibility – it's about looking so normal they never think to look twice.

Keep in mind we hae barely scratched the surface of what Burp Suite can do. This beast of a tool has dozens of modules and hundreds of features I haven't even touched on - from automated scanning to finding SQLi vulnerabilities to fuzzing endpoints. Its a complex tool that rewards those who invest time mastering it. I'll be covering more advanced techniques in future guides.

See you soon. d0ctrine out.

see

 

[mariabennet]

thx bro

 

[fuxet]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Deobfuscating the code takes skill, but its not rocket science. You just need to reverse engineer how the JS created the payload. For those of you whose IQ is below 70 just consult an AI. And if you're feeling like a smartass thinking it's just Base64 for Riskified (though a lot of them just use Base64 encode), it isn't:

But you know me, I love all of you so for this demo I've developed a tool to help deobfuscate fingerprints from popular antidetect solutions. For this demonstration, Ive enabled Riskified but I'll be adding most anti-fraud providers soon.

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

So to make things easier, head to the anti-fraud deobfuscation tool in BinX and select Riskified, and paste our intercepted payload.

After deobfuscation your fingerprint data appears like an open book.

{
  "lat": 37.7749,
  "timezone": 240,
  "timestamp": "1689452187394",
  "cart_id": "7629384105",
  "shop_id": "cf.bstatic.com",
  "referrer": "https://secure.booking.com/",
  "href": "https://cf.bstatic.com/static/tag_container/tag_container/a077563c1795a773c91150dd19adefe98d13fd65.html",
  "riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
  "color_depth": 24,
  "page_id": "9xzp4r",
  "shop": "www.booking.com",
  "hardware_concurrency": 8,
  "has_touch": true,
  "history_length": 7,
  "document_title": "Booking.com",
  "console_error": "console.memory is undefined",
  "battery_error": "Error getBattery()",
  "initial_cookie_state_0": "https",
  "initial_cookie_state_1": "persistent",
  "browser": {
    "productsub": "20030107",
    "is_opr": true,
    "is_firefox": false,
    "ev_len": 42
  },
  "os": {
    "cpu": "Windows NT 10.0",
    "platform": "Win32"
  },
  "webgl": {
    "vendor": "Google Inc.",
    "renderer": "ANGLE (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
  },
  "resolution": {
    "dpr": 1.5,
    "screenh": 1080,
    "screenw": 1920,
    "availh": 1040,
    "availw": 1920,
    "innerh": 900,
    "innerw": 1600,
    "outerh": 1040,
    "outerw": 1920
  },
  "date_string": "Fri Mar 25 2025 14:23:07 GMT-0400 (Eastern Daylight Time)",
  "intl": {
    "locale": "en-GB",
    "num_sys": "latn",
    "cal": "gregory",
    "tz": "America/New_York"
  },
  "downlink_error": "navigator.connection is undefined",
  "nav_plu": "Chrome PDF Plugin,Chrome PDF Viewer,Native Client",
  "nav_lang": "en-GB",
  "page_language_data": {
    "page_language": "en",
    "has_translation": true
  },
  "incognito": {
    "safari": true,
    "chrome_quota": 120,
    "service_worker_undefined": false,
    "is_brave": true
  }
}

You can then make strategic edits to boost trust factors and align with your target profile:

* Hidden text: cannot be quoted. *


Once you've made your changes, obfuscate that shit back and replace the payload in your interception dashboard and FORWARD the request.

This process links your fabricated fingerprint to your cookie. The system thinks youre just another legitimate customer instead of the digital con artist you truly are.

Conclusion

Manipulating antifraud systems with Burp Suite is like having a digital disguise kit. You're not just changing how you look – youre altering what the security cameras see. By positioning Burp between your browser and these systems you can feed them whatever fingerprint you want, without even using an antidetect.

Success depends on understanding exactly what these systems collect and how they interpret it. Analyze your Burp logs to study the antifraud requests before messing with them. Look for patterns in the JSON data. The more you understand what they're checking the more precisely you can manipulate it.

Remember: effective digital deception isnt about invisibility – it's about looking so normal they never think to look twice.

Keep in mind we hae barely scratched the surface of what Burp Suite can do. This beast of a tool has dozens of modules and hundreds of features I haven't even touched on - from automated scanning to finding SQLi vulnerabilities to fuzzing endpoints. Its a complex tool that rewards those who invest time mastering it. I'll be covering more advanced techniques in future guides.

See you soon. d0ctrine out.

Thanks

 

[tranhocpro]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Deobfuscating the code takes skill, but its not rocket science. You just need to reverse engineer how the JS created the payload. For those of you whose IQ is below 70 just consult an AI. And if you're feeling like a smartass thinking it's just Base64 for Riskified (though a lot of them just use Base64 encode), it isn't:

But you know me, I love all of you so for this demo I've developed a tool to help deobfuscate fingerprints from popular antidetect solutions. For this demonstration, Ive enabled Riskified but I'll be adding most anti-fraud providers soon.

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

So to make things easier, head to the anti-fraud deobfuscation tool in BinX and select Riskified, and paste our intercepted payload.

After deobfuscation your fingerprint data appears like an open book.

{
  "lat": 37.7749,
  "timezone": 240,
  "timestamp": "1689452187394",
  "cart_id": "7629384105",
  "shop_id": "cf.bstatic.com",
  "referrer": "https://secure.booking.com/",
  "href": "https://cf.bstatic.com/static/tag_container/tag_container/a077563c1795a773c91150dd19adefe98d13fd65.html",
  "riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
  "color_depth": 24,
  "page_id": "9xzp4r",
  "shop": "www.booking.com",
  "hardware_concurrency": 8,
  "has_touch": true,
  "history_length": 7,
  "document_title": "Booking.com",
  "console_error": "console.memory is undefined",
  "battery_error": "Error getBattery()",
  "initial_cookie_state_0": "https",
  "initial_cookie_state_1": "persistent",
  "browser": {
    "productsub": "20030107",
    "is_opr": true,
    "is_firefox": false,
    "ev_len": 42
  },
  "os": {
    "cpu": "Windows NT 10.0",
    "platform": "Win32"
  },
  "webgl": {
    "vendor": "Google Inc.",
    "renderer": "ANGLE (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
  },
  "resolution": {
    "dpr": 1.5,
    "screenh": 1080,
    "screenw": 1920,
    "availh": 1040,
    "availw": 1920,
    "innerh": 900,
    "innerw": 1600,
    "outerh": 1040,
    "outerw": 1920
  },
  "date_string": "Fri Mar 25 2025 14:23:07 GMT-0400 (Eastern Daylight Time)",
  "intl": {
    "locale": "en-GB",
    "num_sys": "latn",
    "cal": "gregory",
    "tz": "America/New_York"
  },
  "downlink_error": "navigator.connection is undefined",
  "nav_plu": "Chrome PDF Plugin,Chrome PDF Viewer,Native Client",
  "nav_lang": "en-GB",
  "page_language_data": {
    "page_language": "en",
    "has_translation": true
  },
  "incognito": {
    "safari": true,
    "chrome_quota": 120,
    "service_worker_undefined": false,
    "is_brave": true
  }
}

You can then make strategic edits to boost trust factors and align with your target profile:

* Hidden text: cannot be quoted. *


Once you've made your changes, obfuscate that shit back and replace the payload in your interception dashboard and FORWARD the request.

This process links your fabricated fingerprint to your cookie. The system thinks youre just another legitimate customer instead of the digital con artist you truly are.

Conclusion

Manipulating antifraud systems with Burp Suite is like having a digital disguise kit. You're not just changing how you look – youre altering what the security cameras see. By positioning Burp between your browser and these systems you can feed them whatever fingerprint you want, without even using an antidetect.

Success depends on understanding exactly what these systems collect and how they interpret it. Analyze your Burp logs to study the antifraud requests before messing with them. Look for patterns in the JSON data. The more you understand what they're checking the more precisely you can manipulate it.

Remember: effective digital deception isnt about invisibility – it's about looking so normal they never think to look twice.

Keep in mind we hae barely scratched the surface of what Burp Suite can do. This beast of a tool has dozens of modules and hundreds of features I haven't even touched on - from automated scanning to finding SQLi vulnerabilities to fuzzing endpoints. Its a complex tool that rewards those who invest time mastering it. I'll be covering more advanced techniques in future guides.

See you soon. d0ctrine out.

d0c is goat

 

[zzw1994414]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

反混淆代码需要技巧，但并非高深莫测。你只需要逆向分析 JS 创建有效载荷的过程。智商低于 70 的同学，可以咨询一下人工智能。如果你自作聪明，以为 Riskified 只是用 Base64 编码（虽然很多 Riskified 都用 Base64 编码），那可不是：

但你们了解我，我爱你们所有人，所以为了这次演示，我开发了一个工具，用于帮助对来自主流反检测解决方案的指纹进行反混淆。为了这次演示，我启用了Riskified，但我很快会添加大多数反欺诈提供商。

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

因此，为了使事情变得简单，请转到 BinX 中的反欺诈反混淆工具并选择Riskified，然后粘贴我们拦截的有效载荷。

经过反混淆后，您的指纹数据看起来就像一本打开的书。
[代码]
{
“纬度”：37.7749，
“时区”：240，
“时间戳”：“1689452187394”，
"cart_id": "7629384105",
"shop_id": "cf.bstatic.com",
"referrer": "https://secure.booking.com/",
"href": "https://cf.bstatic.com/static/tag_c...a077563c1795a773c91150dd19adefe98d13fd65.html",
“riskified_cookie”：“p8jkl352qxnrtyuvcbm7fds9ghzwe6”，
“颜色深度”：24，
"page_id": "9xzp4r",
"商店": "www.booking.com",
“硬件并发”：8，
"has_touch": true,
"history_length": 7,
"document_title": "Booking.com",
"console_error": "console.memory 未定义",
"battery_error": "获取电池 () 时出错",
"initial_cookie_state_0": "https",
"initial_cookie_state_1": "持久",
“浏览器”：{
"productsub": "20030107",
“is_opr”：是的，
“is_firefox”：false，
“ev_len”：42
}，
“操作系统”：{
“CPU”：“Windows NT 10.0”，
“平台”：“Win32”
}，
“webgl”：{
“供应商”：“Google Inc.”
“渲染器”：“ANGLE（英特尔，英特尔（R）UHD Graphics 620，OpenGL 4.5）”
}，
“解决”： {
“dpr”：1.5，
“屏幕分辨率”：1080，
“screenw”：1920，
"可用"：1040，
"可用"：1920，
“内部”：900，
"innerw": 1600,
"outerh": 1040,
“outerw”：1920
}，
"date_string": "2025 年 3 月 25 日星期五 14:23:07 GMT-0400 (东部夏令时间)",
"国际"：{
“语言环境”：“en-GB”，
“num_sys”：“latn”，
"cal": "gregory",
"tz": "美国/纽约"
}，
"downlink_error": "navigator.connection 未定义",
"nav_plu": "Chrome PDF 插件，Chrome PDF 查看器，本机客户端",
"nav_lang": "en-GB",
"页面语言数据": {
"page_language": "en",
"has_translation": true
}，
“隐身”：{
“Safari”：正确，
“chrome_quota”：120，
“service_worker_undefined”：false，
“is_brave”：真
}
}
[/代码]



然后，您可以进行战略性修改，以提高信任因素并与您的目标形象保持一致：

* 隐藏文字：无法引用。*


完成更改后，将其混淆并替换拦截仪表板中的有效载荷并转发请求。

这个过程会将你伪造的指纹与你的 Cookie 关联起来。系统会认为你只是另一个合法客户，而不是真正的数字骗子。

结论

使用Burp Suite操控反欺诈系统就像拥有一套数字伪装工具。你不仅能改变自己的形象，还能改变安全摄像头的监控画面。将Burp置于浏览器和这些系统之间，你就能为它们提供任何你想要的指纹，甚至无需使用反检测系统。

成功取决于准确理解这些系统收集的数据以及它们如何解读这些数据。在处理Burp日志之前，请先分析它们，研究反欺诈请求。在 JSON 数据中寻找规律。你越了解它们在检查什么，就越能精准地操控它们。

请记住：有效的数字欺骗并不在于隐形——而在于看起来如此正常，以至于他们从来不会多看一眼。

请记住，我们仅仅触及了Burp Suite功能的冰山一角。这款强大的工具拥有数十个模块和数百个我甚至还没触及的功能——从自动扫描到查找 SQLi 漏洞，再到模糊测试终端。它是一款复杂的工具，但投入时间掌握它的人会获得丰厚的回报。我将在未来的指南中介绍更多高级技术。

很快会看到你。d0ctrine out。

c

 

[SilverScribe]

thanks

 

[blockd]

I accidentally clicked on this post. I told myself. Read it. Learn something new....lol

 

[blockd]

View attachment 8294 Tampering Antifraud Requests using Burp Suite

Lots of people have been requesting me for some time now some more guides on how to use Burp. So I figured Id finally cave and drop some knowledge on one of the most powerful tools in your digital arsenal.

Burp is a versatile tool with hundreds of nifty features that can be used beyond just assessing sites - you can check vulnerabilities find hidden endpoints, manipulate web traffic and fuck with those pesky antifraud systems blocking your cards. When you know what you're doing, the possibilities are extensive.

View attachment 8296​

Intercepting Requests

See when you browse any website, theres a constant back-and-forth conversation happening. Your browser (the frontend) sends requests to the website's servers (the backend) which processes them and sends back responses. Its a digital conversation where your browser requests to view products or make purchases, and the server responds accordingly.

Burp Suite plants itself right in the middle of this conversation as a proxy. It's digital eavesdropping – you see every request leaving your browser and every response coming back. More importantly you can pause this conversation, edit whats being transmitted and then let it continue. The server has no fucking clue you just rewrote the script.

View attachment 8297​

This matters because when shopping online your browser isn't just talking to the main website. Its also sending data to hidden antifraud systems like Stripe Radar or Forter that analyze whether you're legitimate or some bot-using scammer. With Burp, you can intercept and manipulate both types of traffic – the main site requests and the sneaky antifraud callbacks happening behind the scenes.

Bypassing CVV Requirement via Intercept

One common application of Burp especially among autistic Binners, is forcing sites to accept cards without CVV. Binners generate cards in bulk and test them using public checkers but most sites require CVV, which is why Burp became such a valuable tool.

Heres the dirty little secret: When you submit payment info at checkout your browser sends a POST request containing all your card details – number, expiry CVV, the works. Using Burp's Intercept feature you can catch this request before it reaches the server and edit that shit however you want.

The trick is to either remove the CVV field entirely:

{"card_number":"4111111111111111","expiry":"12/25""billing_zip":"10001"}

Or replace it with an empty value:

{"card_number":"4111111111111111","expiry":"12/25""cvv":"","billing_zip":"10001"}

If the merchants backend validation is garbage (and you'd be amazed how many major retailers fuck this up) the payment might still process. Some payment gateways configure CVV as "optional" rather than required, and lazy developers often dont enforce proper validation. Heck, I've seen shops before where you can even tamper and change the prices of the items you are checking out.

Other major retailers have similar vulnerabilities that Binners exploit to use their generated cards without any CVVs.

Altering Antifraud Request

Now that you understand the basics of interception let's step it up. We all know modern antifraud systems are sneaky motherfuckers. They inject JavaScript code into the pages you browse, silently collecting mountains of data about you. These scripts track everything from your device configuration to how you move your mouse.

Heres what these scripts typically gather:

• Browser fingerprints (user agent screen resolution, installed fonts)
• Hardware details (GPU info via WebGL rendering CPU cores)
• Mouse movements and click patterns (speed, jitter natural vs. bot-like paths)
• Typing rhythm (how fast you enter data, pauses between keystrokes)
• Whether you're using a headless browser or automation tools (Selenium etc.)

View attachment 8298​

All this data gets packaged and sent to their servers (like m.stripe.com for Stripe or forter.com endpoints) where AI systems decide if youre legit or sketchy.

View attachment 8299​

These systems know their data can be tampered with, so they try to hide it from prying eyes. They'll:

• Base64 encode their payloads
• Use character swapping (like replacing a' with x' and vice versa)
• Obfuscate their JavaScript code
• Split data across multiple requests
• Use custom encoding schemes

But heres the dirty truth: security through obscurity is about as effective as that 414720 you bought for $1. These systems must send data in a format your browser can process which means it's there for the taking if you know where to look.

Practical Example: Riskified in Booking.com

Lets get our hands dirty with Riskified, one of the more notorious fraud prevention systems that's been cockblocking carders left and right. Unlike some half-assed security measures this one actually has some teeth to it.

View attachment 8300​

First, we need to set up interception rules in Burp Suite:

1. Go to Proxy > Options > Intercept Client Requests
2. Add a rule: AND domain name matches c.riskified.com
3. Disable response interception

Now browse around the site and pick a flight and try getting to the checkout page and it will most likely connect first to:

https://beacon.riskified.com/

After connecting here, it downloads the JS needed to fingerprint your system. This isnt casual data collection – it's a full digital cavity search that attempts to send everything about you to:

c.riskified.com

Since weve set up interception the fingerprint won't be sent to Riskifieds servers. If you check the HTTP logs panel, you'll see it trying to send an obfuscated payload containing your digital DNA:

Deobfuscation

Anti-fraud sites obfuscate your fingerprint because if they didnt tampering would be child's play. Its like hiding your house key – sure, it's still there but at least make the thief work for it.

Deobfuscating the code takes skill, but its not rocket science. You just need to reverse engineer how the JS created the payload. For those of you whose IQ is below 70 just consult an AI. And if you're feeling like a smartass thinking it's just Base64 for Riskified (though a lot of them just use Base64 encode), it isn't:

But you know me, I love all of you so for this demo I've developed a tool to help deobfuscate fingerprints from popular antidetect solutions. For this demonstration, Ive enabled Riskified but I'll be adding most anti-fraud providers soon.

​

Binx - Your BIN Lookup Tool

Lookup BIN details, check bank information, card type, brand, and more. Share and explore BIN lists.

binx.cc

So to make things easier, head to the anti-fraud deobfuscation tool in BinX and select Riskified, and paste our intercepted payload.

After deobfuscation your fingerprint data appears like an open book.

{
  "lat": 37.7749,
  "timezone": 240,
  "timestamp": "1689452187394",
  "cart_id": "7629384105",
  "shop_id": "cf.bstatic.com",
  "referrer": "https://secure.booking.com/",
  "href": "https://cf.bstatic.com/static/tag_container/tag_container/a077563c1795a773c91150dd19adefe98d13fd65.html",
  "riskified_cookie": "p8jkl352qxnrtyuvcbm7fds9ghzwe6",
  "color_depth": 24,
  "page_id": "9xzp4r",
  "shop": "www.booking.com",
  "hardware_concurrency": 8,
  "has_touch": true,
  "history_length": 7,
  "document_title": "Booking.com",
  "console_error": "console.memory is undefined",
  "battery_error": "Error getBattery()",
  "initial_cookie_state_0": "https",
  "initial_cookie_state_1": "persistent",
  "browser": {
    "productsub": "20030107",
    "is_opr": true,
    "is_firefox": false,
    "ev_len": 42
  },
  "os": {
    "cpu": "Windows NT 10.0",
    "platform": "Win32"
  },
  "webgl": {
    "vendor": "Google Inc.",
    "renderer": "ANGLE (Intel, Intel(R) UHD Graphics 620, OpenGL 4.5)"
  },
  "resolution": {
    "dpr": 1.5,
    "screenh": 1080,
    "screenw": 1920,
    "availh": 1040,
    "availw": 1920,
    "innerh": 900,
    "innerw": 1600,
    "outerh": 1040,
    "outerw": 1920
  },
  "date_string": "Fri Mar 25 2025 14:23:07 GMT-0400 (Eastern Daylight Time)",
  "intl": {
    "locale": "en-GB",
    "num_sys": "latn",
    "cal": "gregory",
    "tz": "America/New_York"
  },
  "downlink_error": "navigator.connection is undefined",
  "nav_plu": "Chrome PDF Plugin,Chrome PDF Viewer,Native Client",
  "nav_lang": "en-GB",
  "page_language_data": {
    "page_language": "en",
    "has_translation": true
  },
  "incognito": {
    "safari": true,
    "chrome_quota": 120,
    "service_worker_undefined": false,
    "is_brave": true
  }
}

You can then make strategic edits to boost trust factors and align with your target profile:

* Hidden text: cannot be quoted. *


Once you've made your changes, obfuscate that shit back and replace the payload in your interception dashboard and FORWARD the request.

This process links your fabricated fingerprint to your cookie. The system thinks youre just another legitimate customer instead of the digital con artist you truly are.

Conclusion

Manipulating antifraud systems with Burp Suite is like having a digital disguise kit. You're not just changing how you look – youre altering what the security cameras see. By positioning Burp between your browser and these systems you can feed them whatever fingerprint you want, without even using an antidetect.

Success depends on understanding exactly what these systems collect and how they interpret it. Analyze your Burp logs to study the antifraud requests before messing with them. Look for patterns in the JSON data. The more you understand what they're checking the more precisely you can manipulate it.

Remember: effective digital deception isnt about invisibility – it's about looking so normal they never think to look twice.

Keep in mind we hae barely scratched the surface of what Burp Suite can do. This beast of a tool has dozens of modules and hundreds of features I haven't even touched on - from automated scanning to finding SQLi vulnerabilities to fuzzing endpoints. Its a complex tool that rewards those who invest time mastering it. I'll be covering more advanced techniques in future guides.

See you soon. d0ctrine out.

I still haven't seen it