IP Library Granted Patent US 8,732,296
Granted Patent B1
US 8,732,296 · App. 12/436,723 · Granted May 20, 2014

System, method, and computer program product for redirecting IRC traffic identified utilizing a port-independent algorithm and controlling IRC based malware

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,732,296
App. No.
12/436,723
Granted
May 20, 2014
Kind
B1
Abstract

A system, method, and computer program product are provided for redirecting internet relay chat (IRC) traffic identified utilizing a port-independent algorithm and controlling IRC based malware. In use, IRC traffic communicated via a network is identified utilizing a port-independent algorithm. Furthermore, the IRC traffic is redirected to a honeypot.

Claims (44)

1. A method performed by a computing device coupled to a network, the method comprising:

receiving network traffic via a network interface;

differentiating, within the received network traffic, internet relay chat (IRC) traffic by utilizing a programmed processor to apply a port-independent algorithm operable on the payload of the received network traffic, wherein the programmed processor identifies one or more commands included in the IRC traffic, comprising:

identifying commands included in a predetermined temporal location within the IRC traffic, comprising identifying a predetermined number of packets at a beginning of a sequence of packets of the IRC traffic;

redirecting the IRC traffic to a system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic; and

transmitting, based on the collected information, a command to a bot associated with the IRC traffic to prevent future IRC traffic from being communicated over the network with respect to the bot.

2. The method of claim 1 , wherein the redirected IRC traffic includes instructions for controlling the bot.

3. The method of claim 1 , wherein the act of receiving network traffic comprises receiving network traffic with a firewall.

4. The method of claim 1 , further comprising identifying a destination address and a destination port of the IRC traffic, prior to redirecting the IRC traffic to the system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic.

5. The method of claim 4 , further comprising automatically redirecting the network traffic destined for the destination address and the destination port.

6. The method of claim 1 , further comprising:

identifying a source of the IRC traffic; and

automatically redirecting the network traffic sent from the source to the system that attracts IRC traffic for collecting information relating to such IRC traffic.

7. A device, comprising:

a network interface;

a memory or storage unit; and

a processor coupled to the network interface and to the memory or storage unit;

wherein the memory or storage unit is configured to store and the processor is configured to execute instructions to cause the device to:

monitor network traffic received via the network interface;

differentiate, within the received network traffic, internet relay chat (IRC) traffic from other network traffic by utilizing a port-independent algorithm operable on the payload of the received network traffic, by identifying one or more commands included in the IRC traffic, wherein the instructions to cause the device to differentiate by identifying one more commands comprise instructions that when executed cause the device to:

identify commands included in a predetermined temporal location within the IRC traffic, wherein the instructions to identify commands included in a predetermined temporal location within the IRC traffic comprise instructions that when executed cause the device to identify a predetermined number of packets at a beginning of a sequence of packets of the IRC traffic;

redirect the IRC traffic to a system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic; and

transmit, based on the collected information, a command to a bot associated with the IRC traffic to stop future IRC traffic from being communicated over the network with respect to the bot.

8. The device of claim 7 , wherein the redirected IRC traffic includes instructions for controlling the bot.

9. The device of claim 7 , wherein the device comprises a firewall.

10. The device of claim 7 , wherein the instructions to differentiate IRC traffic to identify one or more commands included in the IRC traffic include instructions to compare the one or more commands to predetermined commands.

11. The device of claim 10 , wherein the instructions to compare the one or more commands to predetermined commands include instructions to compare the one or more commands to commands predetermined to be indicative of traffic that uses an IRC protocol.

12. The device of claim 10 , wherein the instructions to differentiate IRC traffic include instructions to differentiate IRC traffic in response to a determination that the commands included in the IRC traffic match the predetermined commands.

13. The device of claim 10 , wherein the instructions to compare the one or more commands to predetermined commands include instructions to compare a signature of one or more of the commands to signatures of one or more predetermined commands.

14. The device of claim 10 , wherein the instructions to differentiate IRC traffic from other network traffic by utilizing the port-independent algorithm comprise instructions to compare a sequence of the commands included in the IRC traffic to predefined sequences of predetermined commands.

15. The device of claim 14 , wherein the predefined sequences of predetermined commands each include a sequence of the predetermined commands predefined to be indicative of traffic that uses an IRC protocol.

16. The device of claim 14 , wherein the instructions to differentiate IRC traffic include instructions to differentiate IRC traffic in response to a determination that the sequence of the commands included in the IRC traffic match one of the predefined sequences of the predetermined commands.

17. The device of claim 7 , wherein the instructions to cause the device further include instructions to cause the device to identify a destination address and a destination port of the IRC traffic, prior to redirecting the IRC traffic to the system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic.

18. The device of claim 17 , wherein the instructions to cause the device further include instructions to cause the device to automatically redirect network traffic destined for the destination address and the destination port.

19. The device of claim 7 , wherein the instructions to cause the device further include instructions to cause the device to identify a source of the IRC traffic and automatically redirect network traffic sent from the source to the system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic.

20. A non-transitory computer-readable medium comprising instructions stored thereon to cause one or more processors to:

monitor network traffic received via a network interface;

differentiate, within the received network traffic, internet relay chat (IRC) traffic from other network traffic utilizing a port-independent algorithm operable on the payload of the received network traffic, by identifying one or more commands included in the IRC traffic, the instructions to cause the one or more processors to differentiate by identifying one or more commands included in the IRC traffic comprising instructions that when executed cause the one or more processors to

identify commands included in a predetermined temporal location within the IRC traffic, wherein the instructions to identify commands included in a predetermined temporal location within the IRC traffic comprise instructions that when executed cause the device to identify a predetermined number of packets at a beginning of a sequence of packets of the IRC traffic;

redirect the IRC traffic to a system that attracts IRC traffic for the purpose of collecting information relating to such IRC traffic; and

transmit, based on the collected information, a command to a bot associated with the IRC traffic to stop future IRC traffic from being communicated over the network with respect to the bot.

21. The non-transitory computer-readable medium of claim 20 , further comprising instructions to cause the one or more processors to:

identify a source of the IRC traffic; and

automatically redirect the network traffic sent from the source to the system that attracts IRC traffic.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE PATENT TITLES AND REMOVE DUPLICATES IN THE SCHEDULE PREVIOUSLY RECORDED AT REEL: 059354 FRAME: 0335. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jun 23, 2022
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 060792/0307 →
SECURITY INTEREST Recorded Mar 3, 2022
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT
Reel/Frame 059354/0335 →
RELEASE OF INTELLECTUAL PROPERTY COLLATERAL - REEL/FRAME 045056/0676 Recorded Mar 2, 2022
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: MCAFEE, LLC
Reel/Frame 059354/0213 →
RELEASE OF INTELLECTUAL PROPERTY COLLATERAL - REEL/FRAME 045055/0786 Recorded Oct 26, 2020
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: MCAFEE, LLC
Reel/Frame 054238/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE PATENT 6336186 PREVIOUSLY RECORDED ON REEL 045056 FRAME 0676. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 22, 2020
From: MCAFEE, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 054206/0593 →
CORRECTIVE ASSIGNMENT TO CORRECT THE REMOVE PATENT 6336186 PREVIOUSLY RECORDED ON REEL 045055 FRAME 786. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 22, 2020
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 055854/0047 →
SECURITY INTEREST Recorded Jan 12, 2018
From: MCAFEE, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 045055/0786 →
SECURITY INTEREST Recorded Jan 12, 2018
From: MCAFEE, LLC
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 045056/0676 →