Posts

Showing posts with the label Google

Claude AI Interview

Your thoughts on AI First, review what would be released publicly Your name and account details won’t be attached, but anyone can read what you make public: your employer, people you know, governments, and strangers. Your country (United States) will also be shared. Hello! I’m an AI interviewer from Anthropic. As AI is becoming more capable and more consequential, we want to hear how it’s showing up in… Expand start Great — let's dive in. To start, what's the last thing you used AI for? AI was last used to write and debug a custom Python script for parsing documentation. Thanks — that gives me a concrete picture. Now, thinking more broadly: can you tell me about your most memorable moment with AI? the most memorable moment was when it first became more organized for letting AI help organize my daily workload, summarize information, and plan projects. That sounds like a shift in how you worked day to day. Can you walk me through what that actually looked like — what were you do...

Bug Bounty Methodology

BUG BOUNTY METHODOLOGY   Deepseek  April 08, 2026 @02:37:30 OPHIEL | Mercury  Suatnalim ***Prompt*:** *create a bug bounty hunter's methodology, designed as a learning course breakdown into 2 categories: Recon & Application Analysis. divide into subcategories of each main category: Mobile—Android; Websites; Applications. Separate by programming language with example scenario how to apply and find using tools and techniques. Present the various payouts and difficulties ranging from easy bugs to hunt all the way to hard bugs. develop a template mind map boilerplate blueprint that can be used as a strategic step guide checklist for crafting an active bug bounty hunt and target identification. End the training course with the techniques and methods that can be used in modern-day to advance, automate, analyze, acquire, and simplify the process using newer technologies or mental strategies and resources to perfect the system. Include a model design for training an AI Bug B...

Unusual Traffic Sending Requests

IP address: 2a09:bac1:7680:578::4d3:69 Time: 2025-12-22T07:11:13Z URL: https://www.google.com/search?q=skms+service+agent&source=hp&sca_esv=5346d96e928e7d71&oq=skms&gs_l=mobile-heirloom-hp.1.3.0i512i433i131j0i512l3j0i512i10.3734.5181.0.8957.5.4.0.1.1.0.171.648.0j4.4.0....0...1.1j4.34.mobile-heirloom-hp..1.4.646.eEN_Ptqa3Po&sei=V6xCaYHBHJ7pwN4PjZr2uQM

Client Domain Hooking

Client Domain Hooking - Example Attack – duszynski.eu – Piotr Duszyński Client Domain Hooking - Example Attack Written on May 20, 2019 In my last blog post I have released a paper that described all relevant technical aspects of the ‘Client Domain Hooking’, along with a HTTP Strict Transport Security (HSTS) survey made for the TOP 1000 Alexa websites. In this post I will show how to run a simulated, ‘Client domain Hooking’ attack which will be used to evaluate an example browser-based application security posture. “Prerequisites” In order to execute this attack, you will need the following set-up: any active and registered domain name (we will be using ‘cdh.modlishka.io’ as an example). a valid wildcard TLS certificate for the domain that we own (it can be either bought or obtained from the “Let’s Encrypt” service). latest version of Modlishka v.1.1 reverse proxy. target applications, such as the latest version of Chrome browser and example vulnerable WebView based mobile applications....