# US 2019/0356636 A1 · Secure Message Inoculation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0356636 A1
- Document ID: US20190356636A1
- Status: Published application
- Kind: A1
- Application number: 16/428,044
- Filed: 2019-05-31
- Published: 2019-11-21
- Earliest claimed: 2016-07-08
- Assignees: XATTIC, Inc.
- Applicants: XATTIC, Inc.
- Inventors: Roman Kagarlitsky
- Web page: https://patentgrep.com/patent/US20190356636A1

## CPC

- H04L 51/066: Format adaptation, e.g. format conversion or compression
- G06F 40/134: Hyperlinking
- G06V 30/224: of printed characters having additional code marks or containing code marks
- H04L 51/08: Annexed information, e.g. attachments
- H04L 51/18: Commands or executable codes
- H04L 63/0281: {Proxies}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- G06V 30/10: Character recognition
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06V: IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING

## Abstract

A message directed to a recipient of a messaging client is intercepted and prevented from reaching the messaging client in a native sent message format as sent from a sender of the message. One or more portions of the message are rendered to a format that is incapable of execution by a device and the message in the format that is incapable of execution is delivered to the messaging client for viewing and/or printing by the recipient.

## Claims

### Claim 1

A method, comprising:
receiving, at a messaging gateway, a message sent from a sender and directed to a recipient associated with a messaging client controlled by the messaging gateway;
rendering, by the messaging gateway, the message in a messaging format to an image format; and
storing, by the messaging gateway, the message in the image format in a location accessible to the messaging client and providing a mechanism for the recipient for accessing the message in the image format.

### Claim 2

A method, comprising:
intercepting, at a gateway, a message directed to a message client;
transforming, by the gateway, the message into an image format;
notifying, by the gateway, a recipient of the message that the message was received; and
providing, by the gateway, the message in the image format for viewing on the message client while preventing the message client from accessing the message in an original format associated with the message.

### Claim 3 (depends on 2)

The method of claim 2, wherein intercepting further includes processing the method as a milter process initiated on the gateway upon receipt of the message directed to the recipient.

### Claim 4 (depends on 2)

The method of claim 2, wherein transforming further includes producing print data for printing the message wherein the print data is in the image format.

### Claim 5 (depends on 2)

The method of claim 2, wherein transforming further includes capturing one or more screenshots of the message while displayed on the gateway to produce the image format.

### Claim 6 (depends on 2)

The method of claim 2, wherein transforming further includes parsing a body of the message to identify embedded links within the message.

### Claim 7 (depends on 6)

The method of claim 6, wherein parsing further includes traversing each link and imaging a source web page associated with that link and adding an imaged version of the source web page as an attachment to the message in the image format.

### Claim 8 (depends on 2)

The method of claim 2, wherein transforming further includes stripping metadata associated with the message from a body of the message.

### Claim 9 (depends on 8)

The method of claim 8, wherein stripping further includes transforming the metadata into a first image file associated with the message and transforming the body of the message as a second image file associated with the message.

### Claim 10 (depends on 2)

The method of claim 2, wherein transforming further includes scanning the message for attachments, opening each attachment, transforming each content of each attachment into one or more images files.

### Claim 11 (depends on 2)

The method of claim 2, wherein notifying further includes constructing a second message and sending the second message to the recipient as a notification that the message in the image format is available for viewing.

### Claim 12 (depends on 2)

The method of claim 2, wherein providing further includes making metadata associated with the message, a body or payload associated with the message, and attachments provided with the message available to the message client as images viewable from the message client.

### Claim 13

A method, comprising:
preventing, by a proxy device, a message that is sent from a sender in an original format from being delivered to a recipient on a message client device;
converting, by the proxy device, the message from the original format into an image format; and
delivering, by the proxy device, the message in the image format to the message client device for access by the recipient.

### Claim 14 (depends on 13)

The method of claim 13, wherein preventing further includes integrating the method into a messaging server associated with the message client device.

### Claim 15 (depends on 13)

The method of claim 13, wherein converting further includes converting a body or a payload of the message into a first image and metadata of the message into a second image.

### Claim 16 (depends on 15)

The method of claim 15, wherein converting further includes converting sites associated with embedded links of the body or the payload into one or more third images.

### Claim 17 (depends on 16)

The method of claim 16, wherein converting further includes converting attachments that were attached to the message into one or more fourth images.

### Claim 18 (depends on 17)

The method of claim 17, wherein delivering further includes attaching the first image, the second image, the one or more third images, and the one or more fourth images into a new message and sending the new message to the recipient at the message client device.

### Claim 19 (depends on 18)

The method of claim 18, wherein attaching further includes providing second metadata for the new message that includes portions of the metadata associated with the message.

### Claim 20

A system, comprising:
a proxy device; and
a message gateway;
wherein the message gateway is configured to: invoke the proxy device when a message is received from a sender and is directed to a recipient of a message client;
wherein the proxy device is configured to: convert the message from an original message format to an image format and provide the message in the image format back to the message gateway;
wherein the message gateway is further configured to: send the message in the image format to the recipient on the message client.

### Claim 21 (depends on 20)

The system of claim 20, wherein the proxy device is further configured to: convert any attachments or any web pages referenced as links in the message to attachment images and provide the message in the image format with the attachment images to the message gateway.
