AGI-Plan: Difference between revisions
Created |
m →top: clean up, typo(s) fixed: 4-6 → 4–6 |
||
(24 intermediate revisions by 17 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|DOS-platform based malware}} |
|||
⚫ | |||
{{More footnotes|date=March 2010}} |
|||
{{Infobox computer virus |
|||
⚫ | |||
| Common name = AGI-Plan |
| Common name = AGI-Plan |
||
| Technical name = Month |
| Technical name = Month 2-4 |
||
| Family = [[Zero Bug (virus)|Zero Bug |
| Family = [[Zero Bug (virus)|Zero Bug]] |
||
| Aliases = |
| Aliases = Month 2-4, Agiplan |
||
| Classification = [[Virus]] |
| Classification = [[Computer Virus|Virus]] |
||
| Type = [[DOS]] |
| Type = [[DOS]] |
||
| Subtype = [[COM]], destructive |
| Subtype = [[COM file|COM]] file, destructive |
||
| IsolationDate = Unknown |
| IsolationDate = Unknown |
||
| Isolation = [[ |
| Isolation = [[Mülheim an der Ruhr]], [[Germany]] |
||
| Origin = Unknown |
| Origin = Unknown |
||
| Author = Unknown |
| Author = Unknown |
||
}} |
}} |
||
'''AGI-Plan''' was a [[ |
'''AGI-Plan''' was a [[memory resident]] [[DOS]] [[file infector]] first isolated at the [[Agiplan (company)|Agiplan]] software company in [[Germany]]. Because of [[Computer Antivirus Research Organization|CARO]] standards that dictate that viruses should not be named after companies, AGI-Plan's technical name is Month 4–6. This name also violates CARO standards, but a more minor rule involving syntax. AGI-Plan is related to the [[Zero Bug (virus)|Zero Bug]] virus, as both it and AGI-Plan prepend 1,536 [[byte]]s to files they infect. |
||
AGI-Plan is not initially damaging until several months after the initial infection, hence its name. After activation, AGI-Plan will begin to corrupt write operations, which results in slow, difficult-to-notice damage |
AGI-Plan is not initially damaging until several months after the initial infection, hence its name. After activation, AGI-Plan will begin to corrupt write operations, which results in slow, difficult-to-notice damage over time.<ref>{{cite web|title=Agiplan|url=http://www.pandasecurity.com/homeusers/security-info/14/Agiplan/|publisher=Panda Security|accessdate=12 February 2013}}</ref> |
||
AGI-Plan is notable for reappearing in [[South Africa]] in what appeared to be an intentional re-release several years after. AGI-Plan never succeeded in spreading |
AGI-Plan is notable for reappearing in [[South Africa]] in what appeared to be an intentional re-release several years after. AGI-Plan never succeeded in spreading significantly beyond the isolated incidents in Germany and South Africa. |
||
==References== |
|||
{{reflist}} |
|||
== External links == |
== External links == |
||
*[http://www.f-secure.com/v-descs/agiplan.shtml Month 4-6], by [[F-Secure]] |
*[http://www.f-secure.com/v-descs/agiplan.shtml Month 4-6], by [[F-Secure]] |
||
[[Category: |
[[Category:DOS file viruses]] |
||
{{malware-stub}} |
Latest revision as of 03:50, 9 March 2022
This article includes a list of general references, but it lacks sufficient corresponding inline citations. (March 2010) |
AGI-Plan | |
---|---|
Technical name | Month 2-4 |
Alias | Month 2-4, Agiplan |
Type | DOS |
Subtype | COM file, destructive |
Classification | Virus |
Family | Zero Bug |
Origin | Unknown |
Authors | Unknown |
AGI-Plan was a memory resident DOS file infector first isolated at the Agiplan software company in Germany. Because of CARO standards that dictate that viruses should not be named after companies, AGI-Plan's technical name is Month 4–6. This name also violates CARO standards, but a more minor rule involving syntax. AGI-Plan is related to the Zero Bug virus, as both it and AGI-Plan prepend 1,536 bytes to files they infect.
AGI-Plan is not initially damaging until several months after the initial infection, hence its name. After activation, AGI-Plan will begin to corrupt write operations, which results in slow, difficult-to-notice damage over time.[1]
AGI-Plan is notable for reappearing in South Africa in what appeared to be an intentional re-release several years after. AGI-Plan never succeeded in spreading significantly beyond the isolated incidents in Germany and South Africa.
References
[edit]External links
[edit]