I know you AC thanks for chiming in. I’m ATP from the TA. Yes I am being watched for sure. To the tune of imaging planes doing grids over my isolated remote location. And I know it is me, I am the only one here. I am chasing down the source that would make them so interested in me. It is closer than we would think. Much closer... Right under our fingers. Working on proving it now. I keep fishing and they will slip up and I will catch it.
Yes I am very familiar with Alphabet and who they are and what they are capable of, I have dealt with them personally in the past. But this particular issue is with general access at Youtube for sure AC. I tested it twice after the first incident and it is part of their general JS script package so everyone is getting hit with it. No one else in my circles uses the security tools I am using because they take extra work to navigate which is inconvenient for most. But even at that I would not have caught the true scope of it being a hitchhiking bot if it had not been for the default IP address security features at the TA. But I can clear out my cache and I am good again so it is not just mine or it would remain in my stuff and persist.
I posted the screenshots to show what I am getting if you can find a few to come drop in over there. As you know you are always welcome, SS can link you to it. NoScript warning lists Youtube specifically as the identity/credential security issue without a doubt. And I picked it up each time I went to YouTube and loaded their JS. They were pulling this same stuff back in 2008 and again in 2012. But back then they were also accessing local machine microphones and cameras along with their keylogging and tracking.
It boils down to this AC, just as important as user security, interacting with YouTube at all has now become a security risk for domain sites also. If they are keylogging credentials and user IP addresses they can gain access aside from the identity issue.
That is amazing. Great catch.