Thanks to everyone who replied. Anyway - the workstation was in a
different building. I had our helpdesk take a look at it and I've
escalated the packet trace (tcpdump) to our AV vendor.
I'll keep you updated on what happened on this.
Thanks once again.
Best,
Tony
On Wed, Nov 11, 2009 at 10:38 AM, Murda Mcloud <murdamcloud (at) bigpond (dot) com [email concealed]> wrote:
> Here's some interesting stuff:
> ==========================================
>
> Results returned from whois.arin.net:
>
>
> OrgName: RIPE Network Coordination Centre
> OrgID: RIPE
> Address: P.O. Box 10096
> City: Amsterdam
> StateProv:
> PostalCode: 1001EB
> Country: NL
>
> ReferralServer: whois://whois.ripe.net:43
>
> NetRange: 77.0.0.0 - 77.255.255.255
> CIDR: 77.0.0.0/8
> NetName: 77-RIPE
> NetHandle: NET-77-0-0-0-1
> Parent:
> NetType: Allocated to RIPE NCC
> NameServer: NS-PRI.RIPE.NET
> NameServer: SEC1.APNIC.NET
> NameServer: SEC3.APNIC.NET
> NameServer: TINNIE.ARIN.NET
> NameServer: NS2.LACNIC.NET
> NameServer: SUNIC.SUNET.SE
> Comment: These addresses have been further assigned to users in
> Comment: the RIPE NCC region. Contact information can be found in
> Comment: the RIPE database at http://www.ripe.net/whois
> RegDate: 2006-08-29
> Updated: 2009-05-18
>
> # ARIN WHOIS database, last updated 2009-11-09 20:00
> # Enter ? for additional hints on searching ARIN's WHOIS database.
>
>
> Results returned from whois.ripe.net:
>
> % This is the RIPE Database query service.
> % The objects are in RPSL format.
> %
> % The RIPE Database is subject to Terms and Conditions.
> % See http://www.ripe.net/db/support/db-terms-conditions.pdf
>
> % Information related to '77.91.227.64 - 77.91.227.127'
>
> inetnum: 77.91.227.64 - 77.91.227.127
> netname: MEGANET
> descr: MEGANET
> country: RU
> admin-c: UDF669-RIPE
> tech-c: UDF669-RIPE
> status: ASSIGNED PA
> mnt-by: RU-WEBALTA-MNT
> changed: lexa (at) wahome (dot) ru [email concealed] 20071205
> source: RIPE
>
> person: Karl Pulneg
> e-mail: karl (at) protected-solution (dot) com [email concealed]
> remarks: Permant str, Office center 5-50
> remarks: =========================================
> remarks: Protected Solution is the Internet System research company
> remarks: We do monitoring and hardware managment, online
> remarks: administration services. Find more at
> www.protected-solution.com
> remarks: Spam issues: abuse (at) protected-solution (dot) com [email concealed]
> remarks: Network security issues: noc (at) protected-solution (dot) com [email concealed]
> remarks: General information: info (at) protected-solution (dot) com [email concealed]
> remarks: ==========================
> abuse-mailbox: abuse (at) protected-solution (dot) com [email concealed]
> address: Protected Solution Ltd (IBC)
> address: PO box 1055
> address: Permant str, Office center 5-50
> address: Victoriya, Mahe, Seychelles
> phone: +248 383 499
> phone: +248 383 501
> nic-hdl: UDF669-RIPE
> changed: admin (at) protected-solution (dot) com [email concealed] 20091031
> source: RIPE
> mnt-by: IDEAL-MNT
>
> % Information related to '77.91.224.0/21AS41947'
>
> route: 77.91.224.0/21
> descr: WEBALTA / Internet Search Company
> descr: Moscow, Russia
> origin: AS41947
> mnt-by: RU-WEBALTA-MNT
> mnt-routes: RU-WEBALTA-MNT
> changed: support (at) webalta (dot) ru [email concealed] 20070524
> source: RIPE
>
>
>
>> >-----Original Message-----
>> >From: listbounce (at) securityfocus (dot) com [email concealed] [mailto:listbounce (at) securityfocus (dot) com [email concealed]]
>> >On Behalf Of Tony Raboza
>> >Sent: Tuesday, November 10, 2009 10:05 PM
>> >To: security-basics (at) securityfocus (dot) com [email concealed]
>> >Subject: Zombie / Botnet?
>> >
>> >Hi,
>> >
>> >One of our workstations is broadcasting a huge amount of UDP traffic
>> >(around 5Mbps) and I'm thinking it could be a zombied computer doing
>> >DDOS as directed by its controller. But the weird thing is - it has
>> >an updated McAfee AV with HIPS ?? Why was this not detected - or
>> >could I be reading this wrong? Here's a portion of the tcpdump:
>> >
>> >14:00:20.509030 IP 192.168.10.10.smpppd > i.root-servers.net.hpstgmgr:
>> >UDP, length 1000
>> >14:00:20.519512 IP 192.168.10.10.iiw-port > 77.91.227.67.4744: UDP,
>> >length 1000
>> >14:00:20.520580 IP 192.168.10.10.odi-port > a.root-servers.net.4496:
>> >UDP, length 1000
>> >14:00:20.521733 IP 192.168.10.10.brcm-comm-port >
>> >b.root-servers.net.4710: UDP, length 1000
>> >14:00:20.523076 IP 192.168.10.10.pcle-infex > c.root-servers.net.826:
>> >UDP, length 1000
>> >14:00:20.524186 IP 192.168.10.10.csvr-proxy > d.root-servers.net.3997:
>> >UDP, length 1000
>> >14:00:20.525251 IP 192.168.10.10.csvr-sslproxy >
>> >E.ROOT-SERVERS.NET.funk-license: UDP, length 1000
>> >14:00:20.526385 IP 192.168.10.10.firemonrcc >
>> >f.root-servers.net.sonuscallsig: UDP, length 1000
>> >14:00:20.527798 IP 192.168.10.10.spandataport >
>> >G.ROOT-SERVERS.NET.4130: UDP, length 1000
>> >14:00:20.528794 IP 192.168.10.10.magbind > h.root-servers.net.atmtcp:
>> >UDP, length 1000
>> >14:00:20.529947 IP 192.168.10.10.ncu-1 >
>> >i.root-servers.net.direcpc-dll: UDP, length 1000
>> >14:00:20.537027 IP 192.168.10.10.ncu-2 > 77.91.227.67.audit-transfer:
>> >UDP, length 1000
>> >14:00:20.538422 IP 192.168.10.10.embrace-dp-s >
>> >77.91.227.67.bluelance: UDP, length 1000
>> >14:00:20.538712 IP 192.168.10.10.embrace-dp-c >
>> >a.root-servers.net.embrace-dp-s: UDP, length 1000
>> >14:00:20.540010 IP 192.168.10.10.dmod-workspace >
>> >b.root-servers.net.bvcontrol: UDP, length 1000
>> >14:00:20.540208 IP 192.168.10.10.tick-port > a.root-servers.net.925:
>> >UDP, length 1000
>> >14:00:20.541412 IP 192.168.10.10.cpq-tasksmart >
>> >b.root-servers.net.bnt-manager: UDP, length 1000
>> >14:00:20.541756 IP 192.168.10.10.intraintra > c.root-servers.net.864:
>> >UDP, length 1000
>> >14:00:20.542941 IP 192.168.10.10.netwatcher-mon >
>> >c.root-servers.net.sbi-agent: UDP, length 1000
>> >14:00:20.544113 IP 192.168.10.10.netwatcher-db >
>> >d.root-servers.net.4467: UDP, length 1000
>> >14:00:20.544400 IP 192.168.10.10.isns > d.root-servers.net.4245: UDP,
>> >length 1000
>> >14:00:20.545444 IP 192.168.10.10.ironmail > E.ROOT-SERVERS.NET.2374:
>> >UDP, length 1000
>> >
>> >
>> >==
>> >
>> >Its sending UDP traffic to the root nameservers ....
>> >
>> >Any ideas?
>> >Thanks.
>> >
>> >
>> >Best,
>> >Tony
>> >
>> >-----------------------------------------------------------------------
-
>> >Securing Apache Web Server with thawte Digital Certificate
>> >In this guide we examine the importance of Apache-SSL and who needs an
>> >SSL certificate. We look at how SSL works, how it benefits your company
>> >and how your customers can tell if a site is secure. You will find out
>> >how to test, purchase, install and use a thawte Digital Certificate on
>> >your Apache web server. Throughout, best practices for set-up are
>> >highlighted to help you ensure efficient ongoing management of your
>> >encryption keys and digital certificates.
>> >
>> >http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be44
2f
>> >727d1
>> >-----------------------------------------------------------------------
-
>
>
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.
different building. I had our helpdesk take a look at it and I've
escalated the packet trace (tcpdump) to our AV vendor.
I'll keep you updated on what happened on this.
Thanks once again.
Best,
Tony
On Wed, Nov 11, 2009 at 10:38 AM, Murda Mcloud <murdamcloud (at) bigpond (dot) com [email concealed]> wrote:
> Here's some interesting stuff:
> ==========================================
>
> Results returned from whois.arin.net:
>
>
> OrgName: RIPE Network Coordination Centre
> OrgID: RIPE
> Address: P.O. Box 10096
> City: Amsterdam
> StateProv:
> PostalCode: 1001EB
> Country: NL
>
> ReferralServer: whois://whois.ripe.net:43
>
> NetRange: 77.0.0.0 - 77.255.255.255
> CIDR: 77.0.0.0/8
> NetName: 77-RIPE
> NetHandle: NET-77-0-0-0-1
> Parent:
> NetType: Allocated to RIPE NCC
> NameServer: NS-PRI.RIPE.NET
> NameServer: SEC1.APNIC.NET
> NameServer: SEC3.APNIC.NET
> NameServer: TINNIE.ARIN.NET
> NameServer: NS2.LACNIC.NET
> NameServer: SUNIC.SUNET.SE
> Comment: These addresses have been further assigned to users in
> Comment: the RIPE NCC region. Contact information can be found in
> Comment: the RIPE database at http://www.ripe.net/whois
> RegDate: 2006-08-29
> Updated: 2009-05-18
>
> # ARIN WHOIS database, last updated 2009-11-09 20:00
> # Enter ? for additional hints on searching ARIN's WHOIS database.
>
>
> Results returned from whois.ripe.net:
>
> % This is the RIPE Database query service.
> % The objects are in RPSL format.
> %
> % The RIPE Database is subject to Terms and Conditions.
> % See http://www.ripe.net/db/support/db-terms-conditions.pdf
>
> % Information related to '77.91.227.64 - 77.91.227.127'
>
> inetnum: 77.91.227.64 - 77.91.227.127
> netname: MEGANET
> descr: MEGANET
> country: RU
> admin-c: UDF669-RIPE
> tech-c: UDF669-RIPE
> status: ASSIGNED PA
> mnt-by: RU-WEBALTA-MNT
> changed: lexa (at) wahome (dot) ru [email concealed] 20071205
> source: RIPE
>
> person: Karl Pulneg
> e-mail: karl (at) protected-solution (dot) com [email concealed]
> remarks: Permant str, Office center 5-50
> remarks: =========================================
> remarks: Protected Solution is the Internet System research company
> remarks: We do monitoring and hardware managment, online
> remarks: administration services. Find more at
> www.protected-solution.com
> remarks: Spam issues: abuse (at) protected-solution (dot) com [email concealed]
> remarks: Network security issues: noc (at) protected-solution (dot) com [email concealed]
> remarks: General information: info (at) protected-solution (dot) com [email concealed]
> remarks: ==========================
> abuse-mailbox: abuse (at) protected-solution (dot) com [email concealed]
> address: Protected Solution Ltd (IBC)
> address: PO box 1055
> address: Permant str, Office center 5-50
> address: Victoriya, Mahe, Seychelles
> phone: +248 383 499
> phone: +248 383 501
> nic-hdl: UDF669-RIPE
> changed: admin (at) protected-solution (dot) com [email concealed] 20091031
> source: RIPE
> mnt-by: IDEAL-MNT
>
> % Information related to '77.91.224.0/21AS41947'
>
> route: 77.91.224.0/21
> descr: WEBALTA / Internet Search Company
> descr: Moscow, Russia
> origin: AS41947
> mnt-by: RU-WEBALTA-MNT
> mnt-routes: RU-WEBALTA-MNT
> changed: support (at) webalta (dot) ru [email concealed] 20070524
> source: RIPE
>
>
>
>> >-----Original Message-----
>> >From: listbounce (at) securityfocus (dot) com [email concealed] [mailto:listbounce (at) securityfocus (dot) com [email concealed]]
>> >On Behalf Of Tony Raboza
>> >Sent: Tuesday, November 10, 2009 10:05 PM
>> >To: security-basics (at) securityfocus (dot) com [email concealed]
>> >Subject: Zombie / Botnet?
>> >
>> >Hi,
>> >
>> >One of our workstations is broadcasting a huge amount of UDP traffic
>> >(around 5Mbps) and I'm thinking it could be a zombied computer doing
>> >DDOS as directed by its controller. But the weird thing is - it has
>> >an updated McAfee AV with HIPS ?? Why was this not detected - or
>> >could I be reading this wrong? Here's a portion of the tcpdump:
>> >
>> >14:00:20.509030 IP 192.168.10.10.smpppd > i.root-servers.net.hpstgmgr:
>> >UDP, length 1000
>> >14:00:20.519512 IP 192.168.10.10.iiw-port > 77.91.227.67.4744: UDP,
>> >length 1000
>> >14:00:20.520580 IP 192.168.10.10.odi-port > a.root-servers.net.4496:
>> >UDP, length 1000
>> >14:00:20.521733 IP 192.168.10.10.brcm-comm-port >
>> >b.root-servers.net.4710: UDP, length 1000
>> >14:00:20.523076 IP 192.168.10.10.pcle-infex > c.root-servers.net.826:
>> >UDP, length 1000
>> >14:00:20.524186 IP 192.168.10.10.csvr-proxy > d.root-servers.net.3997:
>> >UDP, length 1000
>> >14:00:20.525251 IP 192.168.10.10.csvr-sslproxy >
>> >E.ROOT-SERVERS.NET.funk-license: UDP, length 1000
>> >14:00:20.526385 IP 192.168.10.10.firemonrcc >
>> >f.root-servers.net.sonuscallsig: UDP, length 1000
>> >14:00:20.527798 IP 192.168.10.10.spandataport >
>> >G.ROOT-SERVERS.NET.4130: UDP, length 1000
>> >14:00:20.528794 IP 192.168.10.10.magbind > h.root-servers.net.atmtcp:
>> >UDP, length 1000
>> >14:00:20.529947 IP 192.168.10.10.ncu-1 >
>> >i.root-servers.net.direcpc-dll: UDP, length 1000
>> >14:00:20.537027 IP 192.168.10.10.ncu-2 > 77.91.227.67.audit-transfer:
>> >UDP, length 1000
>> >14:00:20.538422 IP 192.168.10.10.embrace-dp-s >
>> >77.91.227.67.bluelance: UDP, length 1000
>> >14:00:20.538712 IP 192.168.10.10.embrace-dp-c >
>> >a.root-servers.net.embrace-dp-s: UDP, length 1000
>> >14:00:20.540010 IP 192.168.10.10.dmod-workspace >
>> >b.root-servers.net.bvcontrol: UDP, length 1000
>> >14:00:20.540208 IP 192.168.10.10.tick-port > a.root-servers.net.925:
>> >UDP, length 1000
>> >14:00:20.541412 IP 192.168.10.10.cpq-tasksmart >
>> >b.root-servers.net.bnt-manager: UDP, length 1000
>> >14:00:20.541756 IP 192.168.10.10.intraintra > c.root-servers.net.864:
>> >UDP, length 1000
>> >14:00:20.542941 IP 192.168.10.10.netwatcher-mon >
>> >c.root-servers.net.sbi-agent: UDP, length 1000
>> >14:00:20.544113 IP 192.168.10.10.netwatcher-db >
>> >d.root-servers.net.4467: UDP, length 1000
>> >14:00:20.544400 IP 192.168.10.10.isns > d.root-servers.net.4245: UDP,
>> >length 1000
>> >14:00:20.545444 IP 192.168.10.10.ironmail > E.ROOT-SERVERS.NET.2374:
>> >UDP, length 1000
>> >
>> >
>> >==
>> >
>> >Its sending UDP traffic to the root nameservers ....
>> >
>> >Any ideas?
>> >Thanks.
>> >
>> >
>> >Best,
>> >Tony
>> >
>> >-----------------------------------------------------------------------
-
>> >Securing Apache Web Server with thawte Digital Certificate
>> >In this guide we examine the importance of Apache-SSL and who needs an
>> >SSL certificate. We look at how SSL works, how it benefits your company
>> >and how your customers can tell if a site is secure. You will find out
>> >how to test, purchase, install and use a thawte Digital Certificate on
>> >your Apache web server. Throughout, best practices for set-up are
>> >highlighted to help you ensure efficient ongoing management of your
>> >encryption keys and digital certificates.
>> >
>> >http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be44
2f
>> >727d1
>> >-----------------------------------------------------------------------
-
>
>
------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.
http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442
f727d1
------------------------------------------------------------------------
[ reply ]