Pe_proyo.a-o


 
Thread Tools Search this Thread
Special Forums Cybersecurity Malware Advisories (RSS) Pe_proyo.a-o
# 1  
Old 01-03-2008
Pe_proyo.a-o

This file infector may be dropped or downloaded from remote sites by other malware.
This file infector drops a copy of itself. This file infector creates a registry entry to enable its automatic execution at every system startup.
It then checks all subkeys listed under a registry key and creates a specific entry for every found subkey. This is done to ensure that the execution of the file infector everytime a debugging event is triggered for each listed subkey.
This file infector infects by prepending its code to target host files. It does not infect files with file size less than 1 KB. It also avoids certain folders. Trend Micro detects infected files as PE_PROYO.A.
This file infector drops hidden copies of itself in all physical and removable drives. It drops an AUTORUN.INF file to automatically execute dropped copies when the drives are accessed.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Moose::Meta::TypeConstraint::Registry(3)		User Contributed Perl Documentation		  Moose::Meta::TypeConstraint::Registry(3)

NAME
Moose::Meta::TypeConstraint::Registry - registry for type constraints VERSION
version 2.1202 DESCRIPTION
This class is a registry that maps type constraint names to Moose::Meta::TypeConstraint objects. Currently, it is only used internally by Moose::Util::TypeConstraints, which creates a single global registry. INHERITANCE
"Moose::Meta::TypeConstraint::Registry" is a subclass of Class::MOP::Object. METHODS
Moose::Meta::TypeConstraint::Registry->new(%options) This creates a new registry object based on the provided %options: o parent_registry This is an optional Moose::Meta::TypeConstraint::Registry object. o type_constraints This is hash reference of type names to type objects. This is optional. Constraints can be added to the registry after it is created. $registry->get_parent_registry Returns the registry's parent registry, if it has one. $registry->has_parent_registry Returns true if the registry has a parent. $registry->set_parent_registry($registry) Sets the parent registry. $registry->get_type_constraint($type_name) This returns the Moose::Meta::TypeConstraint object from the registry for the given name, if one exists. $registry->has_type_constraint($type_name) Returns true if the registry has a type of the given name. $registry->add_type_constraint($type) Adds a new Moose::Meta::TypeConstraint object to the registry. $registry->find_type_constraint($type_name) This method looks in the current registry for the named type. If the type is not found, then this method will look in the registry's parent, if it has one. BUGS
See "BUGS" in Moose for details on reporting bugs. AUTHORS
o Stevan Little <stevan.little@iinteractive.com> o Dave Rolsky <autarch@urth.org> o Jesse Luehrs <doy@tozt.net> o Shawn M Moore <code@sartak.org> o XXXX XXX'XX (Yuval Kogman) <nothingmuch@woobling.org> o Karen Etheridge <ether@cpan.org> o Florian Ragwitz <rafl@debian.org> o Hans Dieter Pearcey <hdp@weftsoar.net> o Chris Prather <chris@prather.org> o Matt S Trout <mst@shadowcat.co.uk> COPYRIGHT AND LICENSE
This software is copyright (c) 2006 by Infinity Interactive, Inc.. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.18.2 2014-01-19 Moose::Meta::TypeConstraint::Registry(3)