Phishing | googleusercontent.com #693
Comments
spirillen
added
help wanted
|
The phishing related content seems to be from 2019 and long since resolved. The tracking issues seem to be with consent of the first-party, so not so relevant here but maybe worth considering still for the matrix. Some examples of the mentioned links from 2019: |
|
Cool, thanks for looking at them, closing as no longer relevant. No longer adding subdomains to (.)google(.) they are blacklisted at the root. then people have to whitelist if they are masochists. |
github-project-automation
bot
moved this from 🆕 New
to ✅ Done
in Phishing Database Backlog
What are the subjects of the phishing (domains, URLs or IPs)?
example.comsub.example.comhttps://example.com/pagehttps://sub.example.com/pageexample.com192.168.0.0/1600f74ba44b80f08e469019d0c9fef3f3e48564247e-apidata.googleusercontent.com|phishing
107.64.70.34.bc.googleusercontent.com|phishing
32.19.192.35.bc.googleusercontent.com|phishing
109.245.225.35.bc.googleusercontent.com|phishing
24.174.232.35.bc.googleusercontent.com|phishing
27.251.247.35.bc.googleusercontent.com|phishing
What are the impersonated domains?
example.orgsub.example.orghttps://example.org/pagehttps://sub.example.org/pageVarious
Where or how did you discover this phishing?
I discovered this phishing by...
I was targeted by this phishing by...
I can see in https://kb.mypdns.org/issue/MTX-40416 (mypdns/matrix#40032) that I have marked some subdomains marked for phishing, anyone who would be able to check if these are still active in phishing?
Do you have a screenshot?
Screenshot
nope
Related external source
googleusercontent.comin Phishing-DatabaseAdditional Information or Context
I have also noticed that...
Response Policy Zone - RPZ
Found these RPZ records in My Privacy DNS
*.googleusercontent.com.strict.adult.mypdns.cloud00f74ba44b80f08e469019d0c9fef3f3e48564247e-apidata.googleusercontent.com.phishing.mypdns.cloud107.64.70.34.bc.googleusercontent.com.phishing.mypdns.cloud109.245.225.35.bc.googleusercontent.com.phishing.mypdns.cloud111.91.190.35.bc.googleusercontent.com.tracking.mypdns.cloud119.29.196.104.bc.googleusercontent.com.tracking.mypdns.cloud175.220.196.104.bc.googleusercontent.com.tracking.mypdns.cloud184.48.190.35.bc.googleusercontent.com.tracking.mypdns.cloud200.94.201.35.bc.googleusercontent.com.adware.mypdns.cloud202.90.190.35.bc.googleusercontent.com.tracking.mypdns.cloud24.174.232.35.bc.googleusercontent.com.phishing.mypdns.cloud246.39.190.35.bc.googleusercontent.com.tracking.mypdns.cloud27.251.247.35.bc.googleusercontent.com.phishing.mypdns.cloud32.19.192.35.bc.googleusercontent.com.phishing.mypdns.cloud42.219.186.35.bc.googleusercontent.com.adware.mypdns.cloud42.219.186.35.bc.googleusercontent.com.tracking.mypdns.cloud49.74.190.35.bc.googleusercontent.com.adware.mypdns.cloud49.74.190.35.bc.googleusercontent.com.tracking.mypdns.cloud64.98.201.35.bc.googleusercontent.com.adware.mypdns.cloud64.98.201.35.bc.googleusercontent.com.tracking.mypdns.cloud84.249.186.35.bc.googleusercontent.com.adware.mypdns.cloud84.249.186.35.bc.googleusercontent.com.tracking.mypdns.cloudaffiliate.googleusercontent.com.adware.mypdns.cloudaffiliate.googleusercontent.com.tracking.mypdns.cloudafs.googleusercontent.com.adware.mypdns.cloudafs.googleusercontent.com.tracking.mypdns.cloudThe text was updated successfully, but these errors were encountered: