Packet capture rate at 14,000 per second without anything running, is my PC compromised ?

edit

@grahamb Thanks for your answer. Is iSCSI traffic generated when 2 computers in the same local network communicating to each other ? When a computer in a local network is compromised by hackers and then it is used to communicate with other computers in the local network, is the traffic that is generated from the communications between them iSCSI ? It is sure that other users plus the owner in the internet shop that I sat in did not do anything. Therefore, the possibility that one of the computers in the shop (192.168.1.210) was compromised to intrude into my computer is most likely.

@grahamb I've gotten a couple more questions from your above answer. Why does the conversation on port 1000 (screenshot https://imgbox.com/CFYDMLd6) correspond to filter "tcp.stream == 4" rather than tcp.stream == 1 or 2 or 3 or 5, etc. ?

After selecting one of the iSCSI packets and using Follow -> TCP Stream, there are a mix of binary, English, JavaScript??, Portuguese and some other languages shown, how to understand the meaning of these binary, Javascript, Portugese, English and what effects do they have on my computer ?

The tcp stream indexes are a synthetic property calculated by Wireshark for each tcp flow (source IP and port, Destination IP and port) as they occur in the capture. The first packet for that flow is the 5th (counting from 0) stream encountered in the capture file. The tcp stream index does not appear anywhere in the traffic.

The stream "Follow" dialog shows what data is being transferred over the stream. As the stream in this case is iSCSI this would seem to be the contents of disk blocks, i.e. files. The data with the light red background is being sent from .142, the data with the light blue background is being sent to .142. I have no idea what the contents are about, but from the protocol used it would seem to be some form of file transfer.

@grahamb Thanks. Is iSCSI traffic generated when 2 computers in the same local network transferring files with each other ? if 192.168.1.210 was compromised, and then it was used to transfer files with my computer 192.168.1.142, then iSCSI traffic would be generated, right?

I'm not that familiar with iSCSI, but yes, it's a networking protocol to transfer files, usually between a client and some form of storage array.

From what I can see it's your PC that's controlling the data transfer and issuing the commands, both reads and writes. Unfortunately the info isn't available from the capture file, but if it happens again you could use other tools to locate the process causing this transfer, e.g. TCPView.

@grahamb I'm pretty sure that I did not command to transfer any file. That's why I'm puzzled. The Wireshark capture file that you checked was captured on February 17. On February 26, I captured traffic again in the same internet shop with both Wireshark and Snort. When this problem was happening (it happens in every internet shop and every time I sit in), I looked up the port in the output of netstat -anp tcp -o and then looked up the corresponding process ID (pid) with task manager (used the 'details' tab) to see which program is using the TCP connection (video recording, timepoint 6:20). I saw that only Windows apps were using TCP connection. Those steps that I did are equivalent to using the tool TCPView, right ?

Unfortunately it would seem that the process responsible for the traffic to .210 port 3260 has PID 4 which is the System process, which is somewhat understandable as it's probably a filesystem driver that's actually generating the traffic.

As to why this is occurring, I have no idea. There is a Windows tool, "iSCSI Initiator" that might show some information on the connection, but I've never used it so can't help any further.

If you still think this is caused by malware you will need to follow up with an appropriate resource for that, e.g. Bleeping Computer Security Forums, it's not a Wireshark related issue.