Trojan.Maliframe!html

Printer Friendly Page

Discovered: July 10, 2007
Updated: July 10, 2007 11:40:58 AM
Type: Trojan
Infection Length: 65 bytes; 67 bytes
Systems Affected: Windows

Trojan.Maliframe!html is a detection for HTML files that contain hidden iframe elements that attempt to perform malicious actions on the computer. This detection is generally encountered when visiting a malicious Web page, which attempts to quietly direct the user to a malicious URL while the current page is loading.

This detection differs from standard virus definitions in that it is used to catch malicious iframe attacks, as opposed to detecting a particular threat. The detection will block an attack at inception, before the malicious code actually arrives on the computer. If your Symantec antivirus produce displays a warning with this name, this is a good indication that the attack has been stopped.

Antivirus Protection Dates

  • Initial Rapid Release version July 10, 2007 revision 007
  • Latest Rapid Release version April 23, 2018 revision 040
  • Initial Daily Certified version July 10, 2007 revision 017
  • Latest Daily Certified version April 24, 2018 revision 003
  • Initial Weekly Certified release date July 11, 2007

Click here for a more detailed description of Rapid Release and Daily Certified virus definitions.

Writeup By: Ben Nahorney

Discovered: July 10, 2007
Updated: July 10, 2007 11:40:58 AM
Type: Trojan
Infection Length: 65 bytes; 67 bytes
Systems Affected: Windows

Background details
The iframe element is not an inherently malicious HTML element. In fact, it has many positive uses. However, over the last number of years, attackers have discovered it is an easy way to carry off malicious code attacks like drive-by downloads. These malicious iframe elements are hosted on malicious websites, or in some cases, legitimate websites that have been hacked and had the iframe element inserted into their Web pages.

While an attack mechanism commonly found in drive-by downloading websites, the use of the iframe element is not limited to Web pages. It could also appear in emails, documents, or any sort of file type that supports HTML.


What is an iframe element?
The iframe element allows Web developers to include HTML content from other sources in their pages. A typical iframe element might look like this:

<iframe name="example" src=" http://www.example.com/example.html" width="640" height="280"></iframe>

A common real-world example that uses iframe elements are online banner ads. An advertiser creates the content in an HTML file that is hosted on a 3rd party website. A Web developer can then call this content within their own pages by adding the URL in an iframe element. The banner add then appears within the Web page they have created.


How are iframes used maliciously?

One of the features of the iframe element is width and height attributes. In most legitimate cases, such as the banner ad example above, a Web developer would specify the pixel size they would like the ad to appear.

However, a malicious attacker often sets these width and height attributes to zero pixels each. As a result, the iframe is invisible in a standard Web page, making it undetectable to the casual user. Such an iframe element might look like this if viewed in the markup:

<iframe name="malicious" src="http://www.example.com/malicious.html" width="0" height="0"></iframe>

The attacker then includes a malicious URL within the element. When a page that contains such an iframe element is visited, the malicious actions are carried out, without any sort of interaction by the visitor.


What sorts of activities can be carried out with a malicious iframe?
This largely depends on the code on the page the user is directed to through the iframe element. Almost anything that can be carried out on a Web page could be performed through an iframe, though one of the more popular malicious activities is using iframe elements in conjunction with exploit packs.

An exploit pack is a malicious program comprised of a group of exploits for known vulnerabilities. There are a wide variety of exploit packs out there, such as Mpack , Neosploit , Fragus , etc. These programs are often stored on a malicious server. When a user visits such a server, the exploit pack attempts to carry out a series of attacks against either the user’s browser or operating system.

If the exploit pack is successful in finding a vulnerability and then compromising the computer, the next stage of the attack can then proceed. This usually entails the downloading of additional malware files onto the compromised computer. In many cases this entails downloaders, infostealers, or back doors.

Iframe elements and exploit packs can also be used as a method of propagation when a Web server is compromised. After a successful attack in these cases, the threat dropped on the compromised computer may scan for Web files, such as .html, .asp, or .php files, adding a malicious iframe element to any that are found. Alternatively, attackers may use a SQL injection attack routine that adds an iframe into the fields of database tables, and thus any subsequent pages generated from the database.


What are the risks?
An iframe attack, the resulting exploit attempts, and the chances that further malicious code will be downloaded poses a relatively high risk of damaging a compromised computer. The risks vary, and depend on the success of the attack, but range from becoming part of a botnet, to loss of data, and even the chance of identity theft.


What can I do to minimize the risks?
As a general rule, users should always run up-to-date antivirus software with real-time protection such as Norton Antivirus, Norton Internet Security, Norton 360 or Symantec Endpoint Protection . In addition, a firewall -- or better still, an Intrusion Prevention System (IPS) -- will help to block back channel activities initiated by these types of malicious programs. Program controls such as those found in Symantec Endpoint Protection can also help to prevent unknown programs such as these from executing in the first place.

In order to prevent the exploit packs from successfully compromising a computer, it is also a good idea to ensure that all relevant security patches are installed.


How can I find out more?
Advanced users can submit a sample to Threat Expert to obtain a detailed report of the system and file system changes caused by a threat.

Recommendations

Symantec Security Response encourages all users and administrators to adhere to the following basic security "best practices":

  • Use a firewall to block all incoming connections from the Internet to services that should not be publicly available. By default, you should deny all incoming connections and only allow services you explicitly want to offer to the outside world.
  • Enforce a password policy. Complex passwords make it difficult to crack password files on compromised computers. This helps to prevent or limit damage when a computer is compromised.
  • Ensure that programs and users of the computer use the lowest level of privileges necessary to complete a task. When prompted for a root or UAC password, ensure that the program asking for administration-level access is a legitimate application.
  • Disable AutoPlay to prevent the automatic launching of executable files on network and removable drives, and disconnect the drives when not required. If write access is not required, enable read-only mode if the option is available.
  • Turn off file sharing if not needed. If file sharing is required, use ACLs and password protection to limit access. Disable anonymous access to shared folders. Grant access only to user accounts with strong passwords to folders that must be shared.
  • Turn off and remove unnecessary services. By default, many operating systems install auxiliary services that are not critical. These services are avenues of attack. If they are removed, threats have less avenues of attack.
  • If a threat exploits one or more network services, disable, or block access to, those services until a patch is applied.
  • Always keep your patch levels up-to-date, especially on computers that host public services and are accessible through the firewall, such as HTTP, FTP, mail, and DNS services.
  • Configure your email server to block or remove email that contains file attachments that are commonly used to spread threats, such as .vbs, .bat, .exe, .pif and .scr files.
  • Isolate compromised computers quickly to prevent threats from spreading further. Perform a forensic analysis and restore the computers using trusted media.
  • Train employees not to open attachments unless they are expecting them. Also, do not execute software that is downloaded from the Internet unless it has been scanned for viruses. Simply visiting a compromised Web site can cause infection if certain browser vulnerabilities are not patched.
  • If Bluetooth is not required for mobile devices, it should be turned off. If you require its use, ensure that the device's visibility is set to "Hidden" so that it cannot be scanned by other Bluetooth devices. If device pairing must be used, ensure that all devices are set to "Unauthorized", requiring authorization for each connection request. Do not accept applications that are unsigned or sent from unknown sources.
  • For further information on the terms used in this document, please refer to the Security Response glossary.

Writeup By: Ben Nahorney

Discovered: July 10, 2007
Updated: July 10, 2007 11:40:58 AM
Type: Trojan
Infection Length: 65 bytes; 67 bytes
Systems Affected: Windows

You may have arrived at this page either because you have been alerted by your Symantec product about this risk, or you are concerned that your computer has been affected by this risk.

Before proceeding further we recommend that you run a full system scan . If that does not resolve the problem you can try one of the options available below.



FOR NORTON USERS
If you are a Norton product user, we recommend you try the following resources to remove this risk.

Removal Tool


If you have an infected Windows system file, you may need to replace them using from the Windows installation CD .


How to reduce the risk of infection
The following resources provide further information and best practices to help reduce the risk of infection.


FOR BUSINESS USERS
If you are a Symantec business product user, we recommend you try the following resources to remove this risk.

Identifying and submitting suspect files
Submitting suspicious files to Symantec allows us to ensure that our protection capabilities keep up with the ever-changing threat landscape. Submitted files are analyzed by Symantec Security Response and, where necessary, updated definitions are immediately distributed through LiveUpdate™ to all Symantec end points. This ensures that other computers nearby are protected from attack. The following resources may help in identifying suspicious files for submission to Symantec.


Removal Tool

If you have an infected Windows system file, you may need to replace them using from the Windows installation CD .


How to reduce the risk of infection
The following resource provides further information and best practices to help reduce the risk of infection.
Protecting your business network



MANUAL REMOVAL
The following instructions pertain to all current Symantec antivirus products.

1. Performing a full system scan
How to run a full system scan using your Symantec product


2. Restoring settings in the registry
Many risks make modifications to the registry, which could impact the functionality or performance of the compromised computer. While many of these modifications can be restored through various Windows components, it may be necessary to edit the registry. See in the Technical Details of this writeup for information about which registry keys were created or modified. Delete registry subkeys and entries created by the risk and return all modified registry entries to their previous values.

Writeup By: Ben Nahorney