hacking: security in practice
meterpreter not working

Even though the payload I implanted on a hackthebox system had the right host and port programmed on it, when I open meterpreter to to listen on the same port that I have on that payload that I run on the other system and still doesn't do anything, it says it's listening but no session pops up even though I have the right port and ip on the payload. What am I doing wrong? Payload IP is my own virtual box ip for Linux and the port on the payload is 4444 and I set meterpreter to listen on port 4444 I swear the IP is right. What do I do?

submitted by /u/Electronic_Ad_5076
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
cry out

I don't know what kind of feedback I will be receiving from this post. BUT, i work minimum wage in a small shop that I assisted a lot online-wise.

So the shop is a pet shop that has an online app/website that I helped upload a lot of items on after agreeing to be paid separately for them. after uploading more than 200 items and making posts online to support their shop they fired me for asking for my money. I felt betrayed and i deleted the items that I made but the company that made the app and website had a backup for them and kept returning them... is there a way to completely delete them?

i would appreciate any advise or assistance

submitted by /u/alaleesh
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Landlord is trying to monopolize wifi in my building

My question is related to what they can do if I get hold of the password.

It is one of those scenarios where there are little wifi hotspot pods all over the hallways.

So I am wondering if they could locate me based on the amount of signal being used in that area. Or if they can locate me by my device, even if I have a VPN?

They are keeping track of people who don't pay for wifi. I am wanting to use their wifi undetected.

Do you think they can track me by my proximity to a specific hotspot pod in the hallway? Or by my device maybe?

Anyway to get past this? I am not allowed to get wifi from any other source (other than my hotspot) within the building. And I don't want to give anymore money to my landlord than I need to. We are not friends.

Is it hard to get the password? I think I might know part of it.

Thanks in advance.

submitted by /u/TransitionProof5729
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Help With Pen Testing HW (professor didnt explain well leading up to assignment0
https://www.reddit.com/r/Pentesting/comments/tvi8vz/help_with_pen_testing_hw_professor_didnt_explain/

Connect to Metasploit2 and Kali (Linux) Submit a word document with the userids and passwords of all of the local accounts where you are able to crack the password. You may use john the ripper or hashcat, your choice goal is to download a file, /etc/shadow this file contains the password hashes for all of the accounts on metasploitable2. Once you have this file in Kali, run john the ripper against it. The rockyou.txt file will get you 3 or 4 of the hashes ​ john --wordlist=/usr/share/wordlists/rockyou.txt shadow submitted by /u/Flashy_Substance_272 (https://www.reddit.com/user/Flashy_Substance_272)
[link] (https://www.reddit.com/r/Pentesting/comments/tvi8vz/help_with_pen_testing_hw_professor_didnt_explain/) [comments] (https://www.reddit.com/r/Pentesting/comments/tvi8vz/help_with_pen_testing_hw_professor_didnt_explain/)

___________________________
@hacking_Attack
@Hacking_Video

Phantun - Transforms UDP Stream Into (Fake) TCP Streams That Can Go Through Layer 3 &Amp; Layer 4 (NAPT) firewalls/NATs
http://www.kitploit.com/2022/04/phantun-transforms-udp-stream-into-fake.html

___________________________
@hacking_Attack
@Hacking_Video

Phantun is a project that obfuscated UDP packets into TCP connections. It aims to achieve maximum performance (https://www.kitploit.com/search/label/Performance) with minimum processing and encapsulation overhead. It is commonly used in environments where UDP is blocked/throttled but TCP is allowed through. Phantun simply converts a stream of UDP packets into obfuscated TCP stream packets. The TCP stack used by Phantun is designed to pass through most L3/L4 stateful/stateless firewalls/NAT devices. It will not be able to pass through L7 proxies. However, the advantage of this approach is that none of the common UDP over TCP performance killer such as retransmissions and flow control will occur. The underlying UDP properties such as out-of-order delivery are fully preserved even if the connection ends up looking like a TCP connection from the perspective of firewalls/NAT devices. Phantun means Phantom TUN, as it is an obfuscator (https://www.kitploit.com/search/label/Obfuscator) for UDP traffic that does just enough work to make it pass through stateful firewall/NATs as TCP packets.
Usage For the example below, it is assumed that Phantun Server listens for incoming Phantun Client connections at port 4567 (the --local option for server), and it forwards UDP packets to UDP server at 127.0.0.1:1234 (the --remote option for server). It is also assumed that Phantun Client listens for incoming UDP packets at 127.0.0.1:1234 (the --local option for client) and connects to Phantun Server at 10.0.0.1:4567 (the --remote option for client). Phantun creates TUN interface for both the Client and Server. For Client, Phantun assigns itself the IP address 192.168.200.2 by default and for Server, it assigns 192.168.201.2 by default. Therefore, your Kernel must have net.ipv4.ip_forward enabled and setup appropriate iptables rules for NAT between your physical NIC address and Phantun's TUN interface address. You may customize the name of Tun interface created by Phantun and the assigned addresses. Please run the executable with -h options to see how to change them. Another way to help understand this network topology (please see the diagram above for an illustration of this topology): Phantun Client is like a machine with private IP address (192.168.200.2) behind a router. In order for it to reach the Internet, you will need to SNAT the private IP address before it's traffic leaves the NIC. Phantun Server is like a server with private IP address (192.168.201.2) behind a router. In order to access it from the Internet, you need to DNAT it's listening port on the router and change the destination IP address to where the server is listening for incoming connections. In those cases, the machine/iptables running Phantun acts as the "router" that allows Phantun to communicate with outside using it's private IP addresses. As of Phantun v0.2.2, IPv6 support for UDP endpoints has been added, however Fake TCP IPv6 support has not been finished yet. To specify an IPv6 address, use the following format: [::1]:1234 with the command line (https://www.kitploit.com/search/label/Command%20Line) options. Back to TOC (https://github.com/dndx/phantun#table-of-contents) 1. Enable Kernel IP forwarding Edit /etc/sysctl.conf, add net.ipv4.ip_forward=1 and run sudo sysctl -p /etc/sysctl.conf. Back to TOC (https://github.com/dndx/phantun#table-of-contents) 2. Add required firewall rules Client Client simply need SNAT enabled on the physical interface to translate Phantun's address into one that can be used on the physical network. This can be done simply with masquerade. Note: change eth0 to whatever actual physical interface name is Back to TOC (https://github.com/dndx/phantun#table-of-contents) Using nftables table inet nat {
chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
iifname tun0 oif eth0 masquerade
}
}

___________________________
@hacking_Attack
@Hacking_Video

Back to TOC (https://github.com/dndx/phantun#table-of-contents) Using iptables iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Back to TOC (https://github.com/dndx/phantun#table-of-contents) Server Server needs to DNAT the TCP listening port to Phantun's TUN interface address. Note: change eth0 to whatever actual physical interface name is and 4567 to actual TCP port number used by Phantun server Back to TOC (https://github.com/dndx/phantun#table-of-contents) Using nftables table ip nat {
chain prerouting {
type nat hook prerouting priority dstnat; policy accept;
iif eth0 tcp dport 4567 dnat to 192.168.201.2
}
}
Back to TOC (https://github.com/dndx/phantun#table-of-contents) Using iptables iptables -t nat -A PREROUTING -p tcp -i eth0 --dport 4567 -j DNAT --to-destination 192.168.201.2
Back to TOC (https://github.com/dndx/phantun#table-of-contents) 3. Run Phantun binaries as non-root (Optional) It is ill-advised to run network facing applications as root user. Phantun can be run fully as non-root user with the cap_net_admin capability. sudo setcap cap_net_admin=+pe phantun_server
sudo setcap cap_net_admin=+pe phantun_client
Back to TOC (https://github.com/dndx/phantun#table-of-contents) 4. Start Phantun daemon Note: Run Phantun executable with -h option to see full detailed options. Server Note: 4567 is the TCP port Phantun should listen on and must corresponds to the DNAT rule specified above. 127.0.0.1:1234 is the UDP Server to connect to for new connections. RUST_LOG=info /usr/local/bin/phantun_server --local 4567 --remote 127.0.0.1:1234
Or use host name with --remote: RUST_LOG=info /usr/local/bin/phantun_server --local 4567 --remote example.com:1234
Back to TOC (https://github.com/dndx/phantun#table-of-contents) Client Note: 127.0.0.1:1234 is the UDP address and port Phantun should listen on. 10.0.0.1:4567 is the Phantun Server to connect. RUST_LOG=info /usr/local/bin/phantun_client --local 127.0.0.1:1234 --remote 10.0.0.1:4567
Or use host name with --remote: RUST_LOG=info /usr/local/bin/phantun_client --local 127.0.0.1:1234 --remote example.com:4567
Back to TOC (https://github.com/dndx/phantun#table-of-contents) MTU overhead Phantun aims to keep tunneling overhead to the minimum. The overhead compared to a plain UDP packet is the following: Standard UDP packet: 20 byte IP header + 8 byte UDP header = 28 bytes Phantun obfuscated UDP packet: 20 byte IP header + 20 byte TCP header = 40 bytes Note that Phantun does not add any additional header other than IP and TCP headers in order to pass through stateful packet inspection! Phantun's additional overhead: 12 bytes. I other words, when using Phantun, the usable payload for UDP packet is reduced by 12 bytes. This is the minimum overhead possible when doing such kind of obfuscation. Back to TOC (https://github.com/dndx/phantun#table-of-contents) MTU calculation for WireGuard For people who use Phantun to tunnel WireGuard® (https://www.wireguard.com/) UDP packets, here are some guidelines on figuring out the correct MTU to use for your WireGuard interface. WireGuard MTU = Interface MTU - IP header (20 bytes) - TCP header (20 bytes) - WireGuard overhead (32 bytes) For example, for a Ethernet interface with 1500 bytes MTU, the WireGuard interface MTU should be set as: 1500 - 20 - 20 - 32 = 1428 bytes The resulted Phantun TCP data packet will be 1500 bytes which does not exceed the interface MTU of 1500. Back to TOC (https://github.com/dndx/phantun#table-of-contents) Version compatibility While the TCP stack is fairly stable, the general expectation is that you should run same minor versions of Server/Client of Phantun on both ends to ensure maximum compatibility. Back to TOC (https://github.com/dndx/phantun#table-of-contents) Performance Performance was tested on AWS t3.xlarge instance with 4 vCPUs and 5 Gb/s NIC. WireGuard was used for tunneling TCP/UDP traffic between two test

___________________________
@hacking_Attack
@Hacking_Video

instances and MTU has been tuned to avoid fragmentation. WireGuard WireGuard + Phantun WireGuard + udp2raw (cipher-mode=none auth-mode=none disable-anti-replay) iperf3 -c IP -R 1.56 Gbit/s 540 Mbit/s 369 Mbit/s iperf3 -c IP 1.71 Gbit/s 519 Mbit/s 312 Mbit/s Back to TOC (https://github.com/dndx/phantun#table-of-contents) Future plans IPv6 support for fake-tcp Load balancing a single UDP stream into multiple TCP streams Integration tests Auto insertion/removal of required firewall rules Back to TOC (https://github.com/dndx/phantun#table-of-contents) Compariation to udp2raw udp2raw (https://github.com/wangyu-/udp2raw-tunnel) is another popular project by @wangyu- (https://github.com/wangyu-) that is very similar to what Phantun can do. In fact I took inspirations of Phantun from udp2raw. The biggest reason for developing Phantun is because of lack of performance when running udp2raw (especially on multi-core systems such as Raspberry Pi). However, the goal is never to be as feature complete as udp2raw and only support the most common use cases. Most notably, UDP over ICMP and UDP over UDP mode are not supported and there is no anti-replay nor encryption (https://www.kitploit.com/search/label/Encryption) support. The benefit of this is much better performance overall and less MTU overhead because lack of additional headers inside the TCP payload. Here is a quick overview of comparison between those two to help you choose: Phantun udp2raw UDP over FakeTCP obfuscation ✅ ✅ UDP over ICMP obfuscation ❌ ✅ UDP over UDP obfuscation ❌ ✅ Multi-threaded ✅ ❌ Throughput Better Good Raw IP mode TUN interface Raw sockets + BPF Tunneling MTU overhead 12 bytes 44 bytes Seprate TCP connections for each UDP connection Client/Server Server only Anti-replay, encryption ❌ ✅ IPv6 UDP only ✅ Back to TOC (https://github.com/dndx/phantun#table-of-contents) License Copyright 2021-2022 Datong Sun (dndx@idndx.com (mailto:dndx@idndx.com)) Licensed under the Apache License, Version 2.0 or the MIT license , at your option. Files in the project may not be copied, modified, or distributed (https://www.kitploit.com/search/label/Distributed) except according to those terms. Back to TOC (https://github.com/dndx/phantun#table-of-contents)

Download Phantun (https://github.com/dndx/phantun)

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Developing and penetration Testing

Hi, I’m reza azizi ( re2a.official)/on instagram
++++++++++++++++++++++++

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
The Defeat of Cryptocurrency?

https://cdn-images-1.medium.com/max/1920/1*JyAqgCDDR_NpkuU3tIl_nA.jpeg
We’re not poking fun at those trying to make a living or fortune in cryptocurrency markets, but they do have an uphill battle at times…

Continue reading on Coinmonks »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Resources that help you find out the IP address of your conversation partner using IP Logger

https://cdn-images-1.medium.com/max/1024/1*eo1SHrC8AZgwCYEHcjWSfA.jpeg
IP Logger is an easy way to find out a person’s IP address. Today we will look at useful resources and methods that will help us to do…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Bitcoin wallet breakdown — OSINT

https://cdn-images-1.medium.com/max/1197/1*bvtXYrfWXXhL6m7aTQAgEA.jpeg
It’s no longer a secret that bitcoin is not as anonymous as many people think. The balance of the wallet and all of its transfers can be…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
Phantun - Transforms UDP Stream Into (Fake) TCP Streams That Can Go Through Layer 3 &Amp; Layer 4 (NAPT) firewalls/NATs

https://blogger.googleusercontent.com/img/a/AVvXsEhKsoH6RpV4RUYfyjHOJzCK8BF8FEtCZyKvu7EyMX4BZt_vOfJB9EQjnPjw7kpbrW41WQiGn3bhUFPN3Q21j9W05Ir1bHTl3QAmRRf8rNSjvzdpNXzrjMNCMTjuUAl7LMFI2PkE93LpA2Al_iDVuKEdrU_eibiZiiRmn1RjHDoqH2R77Q-P0H7W7Q8k=w640-h302 Phantun is a project that obfuscated UDP packets into TCP connections. It aims to achieve maximum performance with minimum processing and encapsulation overhead.

It is commonly used in environments where UDP is blocked/throttled but TCP is allowed through.

Phantun simply converts a stream of UDP packets into obfuscated TCP stream packets. The TCP stack used by Phantun is designed to pass through most L3/L4 stateful/stateless firewalls/NAT devices. It will not be able to pass through L7 proxies. However, the advantage of this approach is that none of the common UDP over TCP performance killer such as retransmissions and flow control will occur. The underlying UDP properties such as out-of-order delivery are fully preserved even if the connection ends up looking like a TCP connection from the perspective of firewalls/NAT devices.

Phantun means Phantom TUN, as it is an obfuscator for UDP traffic that does just enough work to make it pass through stateful firewall/NATs as TCP packets. UsageFor the example below, it is assumed that Phantun Server listens for incoming Phantun Client connections at port 4567(the --localoption for server), and it forwards UDP packets to UDP server at 127.0.0.1:1234(the --remoteoption for server).

It is also assumed that Phantun Client listens for incoming UDP packets at 127.0.0.1:1234(the --localoption for client) and connects to Phantun Server at 10.0.0.1:4567(the --remoteoption for client).

Phantun creates TUN interface for both the Client and Server. For Client, Phantun assigns itself the IP address 192.168.200.2by default and for Server, it assigns 192.168.201.2by default. Therefore, your Kernel must have net.ipv4.ip_forwardenabled and setup appropriate iptables rules for NAT between your physical NIC address and Phantun's TUN interface address.

You may customize the name of Tun interface created by Phantun and the assigned addresses. Please run the executable with -hoptions to see how to change them.

Another way to help understand this network topology (please see the diagram above for an illustration of this topology):

Phantun Client is like a machine with private IP address (192.168.200.2) behind a router. In order for it to reach the Internet, you will need to SNAT the private IP address before it's traffic leaves the NIC.

Phantun Server is like a server with private IP address (192.168.201.2) behind a router. In order to access it from the Internet, you need to DNATit's listening port on the router and change the destination IP address to where the server is listening for incoming connections.

In those cases, the machine/iptables running Phantun acts as the "router" that allows Phantun to communicate with outside using it's private IP addresses.

As of Phantun v0.2.2, IPv6 support for UDP endpoints has been added, however Fake TCP IPv6 support has not been finished yet. To specify an IPv6 address, use the following format: [::1]:1234with the command line options. Back to TOC 1. Enable Kernel IP forwardingEdit /etc/sysctl.conf, add net.ipv4.ip_forward=1and run sudo sysctl -p /etc/sysctl.conf. Back to TOC 2. Add required firewall rulesClientClient simply need SNAT enabled on the physical interface to translate Phantun's address into one t[...]

___________________________
@hacking_Attack
@Hacking_Video

hat can be used on the physical network. This can be done simply with masquerade.

Note: change eth0to whatever actual physical interface name is Back to TOC Using nftablestable inet nat {
chain postrouting {
type nat hook postrouting priority srcnat; policy accept;
iifname tun0 oif eth0 masquerade
}
} Back to TOC Using iptablesiptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Back to TOC ServerServer needs to DNAT the TCP listening port to Phantun's TUN interface address.

Note: change eth0to whatever actual physical interface name is and 4567to actual TCP port number used by Phantun server Back to TOC Using nftablestable ip nat {
chain prerouting {
type nat hook prerouting priority dstnat; policy accept;
iif eth0 tcp dport 4567 dnat to 192.168.201.2
}
} Back to TOC Using iptablesiptables -t nat -A PREROUTING -p tcp -i eth0 --dport 4567 -j DNAT --to-destination 192.168.201.2 Back to TOC 3. Run Phantun binaries as non-root (Optional)It is ill-advised to run network facing applications as root user. Phantun can be run fully as non-root user with the cap_net_admincapability. sudo setcap cap_net_admin=+pe phantun_server
sudo setcap cap_net_admin=+pe phantun_client Back to TOC 4. Start Phantun daemonNote: Run Phantun executable with -hoption to see full detailed options. ServerNote: 4567is the TCP port Phantun should listen on and must corresponds to the DNAT rule specified above. 127.0.0.1:1234is the UDP Server to connect to for new connections. RUST_LOG=info /usr/local/bin/phantun_server --local 4567 --remote 127.0.0.1:1234 Or use host name with --remote: RUST_LOG=info /usr/local/bin/phantun_server --local 4567 --remote example.com:1234 Back to TOC ClientNote: 127.0.0.1:1234is the UDP address and port Phantun should listen on. 10.0.0.1:4567is the Phantun Server to connect. RUST_LOG=info /usr/local/bin/phantun_client --local 127.0.0.1:1234 --remote 10.0.0.1:4567 Or use host name with --remote: RUST_LOG=info /usr/local/bin/phantun_client --local 127.0.0.1:1234 --remote example.com:4567 Back to TOC MTU overheadPhantun aims to keep tunneling overhead to the minimum. The overhead compared to a plain UDP packet is the following:

Standard UDP packet: 20 byte IP header + 8 byte UDP header = 28 bytes

Phantun obfuscated UDP packet: 20 byte IP header + 20 byte TCP header = 40 bytes

Note that Phantun does not add any additional header other than IP and TCP headers in order to pass through stateful packet inspection!

Phantun's additional overhead: 12 bytes. I other words, when using Phantun, the usable payload for UDP packet is reduced by 12 bytes. This is the minimum overhead possible when doing such kind of obfuscation. Back to TOC MTU calculation for WireGuardFor people who use Phantun to tunnel WireGuard® UDP packets, here are some guidelines on figuring out the correct MTU to use for your WireGuard interface.

WireGuard MTU = Interface MTU - IP header (20 bytes) - TCP header (20 bytes) - WireGuard overhead (32 bytes)

For example, for a Ethernet interface with 1500 bytes MTU, the WireGuard interface MTU should be set as:

1500 - 20 - 20 - 32 = 1428 bytes

The resulted Phantun TCP data packet will be 1500 bytes which does not exceed the interface MTU of 1500. Back to TOC Version compatibilityWhile the TCP stack is fairly stable, the general expectation is that you should run same minor versions of Server/Client of Phantun on both ends to ensure maximum compatibility. Back to TOC PerformancePerformance was tested on AWS t3.xlarge instance with 4 vCPUs and 5 Gb/s NIC. WireGuard was used for tunneling TCP/UDP traffic between two test instances and MTU has been tuned to avoid fragmentation.
WireG[...]

___________________________
@hacking_Attack
@Hacking_Video

uard WireGuard + Phantun WireGuard + udp2raw (cipher-mode=none auth-mode=none disable-anti-replay) iperf3 -c IP -R 1.56 Gbit/s 540 Mbit/s 369 Mbit/s iperf3 -c IP 1.71 Gbit/s 519 Mbit/s 312 Mbit/s Back to TOC Future plans* IPv6 support for fake-tcp
* Load balancing a single UDP stream into multiple TCP streams
* Integration tests
* Auto insertion/removal of required firewall rules Back to TOC Compariation to udp2rawudp2raw is another popular project by @wangyu- that is very similar to what Phantun can do. In fact I took inspirations of Phantun from udp2raw. The biggest reason for developing Phantun is because of lack of performance when running udp2raw (especially on multi-core systems such as Raspberry Pi). However, the goal is never to be as feature complete as udp2raw and only support the most common use cases. Most notably, UDP over ICMP and UDP over UDP mode are not supported and there is no anti-replay nor encryption support. The benefit of this is much better performance overall and less MTU overhead because lack of additional headers inside the TCP payload.

Here is a quick overview of comparison between those two to help you choose:
Phantun udp2raw UDP over FakeTCP obfuscation
✅

✅
UDP over ICMP obfuscation
❌

✅
UDP over UDP obfuscation
❌

✅
Multi-threaded
✅

❌
Throughput Better Good Raw IP mode TUN interface Raw sockets + BPF Tunneling MTU overhead 12 bytes 44 bytes Seprate TCP connections for each UDP connection Client/Server Server only Anti-replay, encryption
❌

✅
IPv6 UDP only
✅ Back to TOC LicenseCopyright 2021-2022 Datong Sun (dndx@idndx.com)

Licensed under the Apache License, Version 2.0 or the MIT license , at your option. Files in the project may not be copied, modified, or distributed except according to those terms. Back to TOC Download Phantun

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
How to start doing Bug Bountys?

I'd like to get into bug bounty hunting. Where is a good place to start? I'd prefer to go for the low hanging fruit that more advanced people would pass up.

Also, is it plausible to get into this with Burp Suite community edition or do you need the pro version to have a chance at being successful?

submitted by /u/Practical_Bathroom53
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Hacking a Samsung Note 8 Pen

Hi!

Not sure if this is the right sub for this but, I need to figure out, if possible, how to hack into my Samsung Note 8 Pen to use on my Google Pixel 6 phone. If I'm in the wrong sub, please don't hesitate to let me know. Or if this isn't even possible.

❤️

submitted by /u/Loverofallanimals66
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
How to recover deleted files that are not in the recycle bin.

https://cdn-images-1.medium.com/max/1202/1*E4R1J5PoHjxpZrV_EYAf5w.jpeg
It is easy enough to accidentally delete files from your computer. But recovering them can be problematic. Especially if you don’t know…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Desanonimización de anónimos con Canarytokens

https://cdn-images-1.medium.com/max/1280/1*wZtXlJgiFuxB4uQQonEChg.jpeg
Los Canarytokens (https://canarytokens.org/) son un tipo de enlace único personalizado en el que alguien hace clic o accede, podemos…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video