Fork Bomb


A fork bomb is a type of denial-of-service (DoS) attack in which a process infinitely replicates itself, consuming system resources and eventually causing a system to crash or become unresponsive. This malicious code exploits the process creation mechanism in an operating system, creating a cascade of processes that replicate exponentially. Fork bombs are typically small and simple, making them difficult to detect and defend against.


The phonetic representation of the keyword “Fork Bomb” using the International Phonetic Alphabet (IPA) is:/ˈfɔːrk ˈbɒm/Where:- “Fork” is pronounced as /ˈfɔːrk/; ‘f’ as in ‘fork,’ ‘ɔː’ as in ‘door’, and ‘rk’ together as in ‘park.’- “Bomb” is pronounced as /ˈbɒm/; ‘b’ as in ‘bomb,’ ‘ɒ’ as in ‘hot,’ and ‘m’ as in ‘mom.’

Key Takeaways

  1. A fork bomb is a form of denial-of-service (DoS) attack that recursively replicates processes, causing system resources to be consumed until the system becomes unresponsive or crashes.
  2. A fork bomb typically exploits a vulnerability in a system’s process creation mechanisms and can be written in various programming languages, including shell scripts, C, and Python.
  3. Preventing a fork bomb involves system administrators implementing resource limits to confine the number of processes a user can run, carefully monitoring running processes, and using intrusion detection systems to identify malicious activity.


The term “Fork Bomb” is important in the field of technology because it refers to a type of denial-of-service (DoS) attack that can significantly disrupt computer systems and networks.

A fork bomb is a malicious program or script designed to replicate itself rapidly, continuously creating child processes that consume system resources such as memory and CPU time.

As a result, the performance of the affected system deteriorates, potentially leading to crashes or a complete freeze.

Understanding fork bomb attacks is critical in implementing appropriate security measures, such as limiting the number of processes a user can run simultaneously or employing intrusion detection systems, to protect vulnerable systems and maintain their stability and reliability.


A fork bomb is unique from other types of cyber attacks, as its primary objective is not to steal or alter data, but rather to incapacitate the targetted computer system or network by consuming all available resources. It is an instance of a wabbit (a type of software that operates recursively) or a form of Denial of Service (DoS) attack, which saturates the system’s capacity to carry out other tasks.

By exploiting the vulnerabilities of the system, a fork bomb triggers a chain reaction in which the system continually repeats processes, overwhelming its capacity to function effectively. Although they do not often cause permanent damage, fork bombs can paralyze the system being targeted, requiring administrators to shut down and reboot the environment, hampering productivity and operational efficiency.

Fork bombs are typically executed in the form of a small piece of malicious code or script that relies on the target system’s forking mechanism – the process by which a program creates a new identical process. As the code continues to duplicate itself exponentially, it quickly consumes available system resources, such as the central processing unit (CPU) time and memory.

To prevent fork bombs from wreaking havoc on a system, developers can implement security measures such as establishing process limits and priorities, as well as employing antivirus and intrusion detection systems to detect and defend against these types of attacks. While fork bombs may not result in permanent damage, system administrators and developers must remain vigilant to mitigate the debilitating effect they can have on system operations.

Examples of Fork Bomb

A fork bomb is a type of denial-of-service (DoS) attack, where a process repeatedly replicates itself to exhaust available system resources, eventually causing the system to slow down or crash. Here are three real-world examples of fork bomb attacks:

2009 University Fork Bomb:In 2009, a computer science student in the United States, upset over bad grades, deployed a fork bomb on his university’s computer network. As a result, the entire network of the institute was brought to a halt for several hours. The student was subsequently caught and faced disciplinary actions.

Social Media Bait and Crash:In 2016, numerous cases were reported on social media where malicious users tricked others into running fork bomb commands on their own systems. These incidents usually involved deceiving the victim by making the command appear to enable a “hidden feature” or provide a “cool tweak” for their computer. Upon executing the command, unaware users suffered system crashes or a significant slowdown of their computers.

Code Misuse by Mistake:There are instances in which developers accidentally include fork bomb code in their software. One such example is when a developer working on a large software project inadvertently added a fork bomb command to one of the test scripts. When the entire team of developers pulled the updates and ran the tests, it caused their computers to slow down or crash, stalling progress on the project until the issue was discovered and resolved.

Fork Bomb FAQ

What is a fork bomb?

A fork bomb is a type of denial-of-service attack that involves recursively creating child processes until a system’s resources are consumed, causing the system to become unresponsive or crash.

How does a fork bomb work?

A fork bomb works by executing a small piece of code that repeatedly replicates itself, creating new processes that consume system resources. As the number of processes increases exponentially, the system becomes overloaded and ultimately fails.

What is the purpose of a fork bomb?

A fork bomb is typically used to intentionally disrupt the normal operation of a computer, server, or network by consuming system resources. Its primary purpose is to cause a denial-of-service, making the targeted system unavailable to its intended users.

How can I protect my system from a fork bomb?

To protect your system from a fork bomb, you can implement resource controls and limits for processes, such as process limits per user and maximum process limits. Additionally, running regular security checks, keeping your software up-to-date, and employing antivirus software can also help prevent and detect fork bomb attacks.

What are some examples of fork bombs?

Example of a fork bomb in Unix/Linux systems is the “fork bomb” shell script:

:(){ :|:& };:

For Windows, a fork bomb can be created using a batch file with the following code:


These examples are provided for educational purposes and should not be used maliciously.

Related Technology Terms

  • Process multiplication
  • System overload
  • Recursive function
  • Denial of service (DoS)
  • Resource exhaustion

Sources for More Information


About The Authors

The DevX Technology Glossary is reviewed by technology experts and writers from our community. Terms and definitions continue to go under updates to stay relevant and up-to-date. These experts help us maintain the almost 10,000+ technology terms on DevX. Our reviewers have a strong technical background in software development, engineering, and startup businesses. They are experts with real-world experience working in the tech industry and academia.

See our full expert review panel.

These experts include:


About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

More Technology Terms

Technology Glossary

Table of Contents