LinuxCommandLibrary

infection

Infect files with test viruses

TLDR

Analyze code using the configuration file (or create one if it does not exist)

$ infection
copy

Use a specific number of threads
$ infection [[-j|--threads]] [number_of_threads]
copy

Specify a minimum Mutation Score Indicator (MSI)
$ infection --min-msi [percentage]
copy

Specify a minimum covered code MSI
$ infection --min-covered-msi [percentage]
copy

Use a specific test framework (defaults to PHPUnit)
$ infection --test-framework [phpunit|phpspec]
copy

Only mutate lines of code that are covered by tests
$ infection --only-covered
copy

Display the mutation code that has been applied
$ infection [[-s|--show-mutations]]
copy

Specify the log verbosity
$ infection --log-verbosity [default|all|none]
copy

SYNOPSIS

infection [options] [arguments]  (non-standard; no official syntax)

DESCRIPTION

The 'infection' command does not exist in standard Linux distributions or common repositories such as those for Ubuntu, Fedora, Debian, or Arch Linux. A search across man pages, coreutils, busybox, and typical system tools yields no results for 'infection'. It is not part of any POSIX standard, GNU coreutils, or major package managers like apt, yum, or pacman.

This term may refer to malware, viruses, or fictional scenarios in cybersecurity training (e.g., CTFs or penetration testing challenges), but no legitimate executable or built-in shell command by this name exists. If encountered in a custom script, third-party software, or malicious context, it could indicate a trojan or custom payload designed to simulate infection mechanics, such as propagating files or network exploits. Users should scan systems with tools like clamav or rkhunter if suspecting compromise.

In legitimate contexts, 'infection' might appear in logs or error messages related to biological simulations, game mods, or academic research software, but never as a core system command. Always verify unfamiliar commands with which infection, type infection, or man infection, which will confirm its absence.

CAVEATS

Command does not exist; attempting to run it results in 'command not found'. Potential security risk if present on system.

SECURITY NOTE

If 'infection' appears in processes or scripts, treat as potential malware. Use ps aux | grep infection and investigate.

ALTERNATIVES FOR SIMULATION

For infection modeling (e.g., epidemiology), use tools like NetLogo or Python libraries such as ndlib, not system commands.

HISTORY

No development history; never included in Linux kernels, distributions, or standards bodies like POSIX or LSB.

SEE ALSO

which(1), type(1), man(1), clamscan(1)

Copied to clipboard