![]() Of this software and associated documentation files (the "Software"), to deal Permission is hereby granted, free of charge, to any person obtaining a copy I believe that when dealing with large amounts of non-descript information such as pseudo-anonymous IP logs, how you present that data is key, alongside what data you can collect, and most of that data the user's web browser will tell you freely upon executing custom javascript code. This is a tool I originally made back around 2019 for my digital advertising business VOXDSP, to identify fraudulent or bot traffic from traffic suppliers, however, I recently decided to adapt it for a more general-purpose that common internet users would be more likely to find of use. Also considering that you are providing links to videos, this alone can infer a lot about a user's interests or viewing preferences over time. These kinds of details can help you identify the original clicker by asking a few suggestive questions in public chats or directly to users you suspect the clicker to be. For example, in the user agent (UA) the mobile or desktop device and browser used will be listed, and the panel will list the phone technical specifications such as memory, CPU count, GPU type, etc, and connection information such as how the user is connecting to the internet be it via WIFI or Cellular. Once data is presented in such a manner, it can be easier to visually infer correlations in the data which can help identify the original clicker. This is why I designed the user interface view.php with emphasis on this fact to ensure it loaded relevant statistics about a clicking user in a way that is easy on the eye, all fitting on-screen elegantly and concisely with relevant tooltips. The problem when IP logging is that unless you send a specific user a logging link in private, it can be hard to know who exactly clicked and what any of that means to you as the logger. This was designed with the intention that no logging URL would be used for more than a few thousand clicks. ![]() view.php is not designed to load millions of IP addresses and simple file-based logs in this manner will reach a 4GB limit on FAT32 without forking to historical log files. This is a simple and lightweight utility, designed to log and view a few thousand IP addresses at maximum. It's not a big deal as it does not reduce the effectiveness of the vector but does allow external parties performing an investigation to identify the kind of information being logged if so desired. I could encrypt or at the very least base64 the url parameters being sent to the server from the Javascript payload, but I don't. Timestamps are baked into the User Agent (UA) string. There are other logs produced, just explore the which is a log of all users whom clicked a URL - this is helpful in cases where some users failed to load the Javascript payload either due to NoScript or closing the page instantly after clicking. To view the list of users who clicked the URL: This is the URL that you distribute to users you intend to grab the IP address of. (it's going to generate log files as plain text)Ĭreate a URL to point at this To create a logging URL: (will use the original YouTube video metadata and redirect to the original video when clicked)Ī URL will be generated and provided as the body of the request-response (HTML page). ![]() No external dependencies are required other than NGINX and PHP-FPM.Ĭlient Dependencies: HTML, CSS, Javascript InstructionsĬopy the contents of this git to your root www directory and setup permissions so that the PHP files can create new files within that directory. This is a simple to setup IP logger that is capable of detecting a user's true country of origin even while behind a VPN, in most cases. A javascript "IP Grabber" that disguises itself behind YouTube metadata.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |