So ...(sigh) what do you do when you complain to a given ISP provider about
a case of attempted abuse by one of their IP addresses and you get a
response from someone in the "security team" whose email name is "cracker?"
Apparently some (or many) of these crackers own (with their consent or not)
even their ISP providers --or worse, some (or many) ISP providers may be
crackers themselves!
A portion of my original complaint to the ISP --where I list one of the
attempted abuse records by the cracker for informational purposes:
----------------------------------------------------------------------------------
from myself <my_emai_address> tonetwork-adm@hinet.net,
network-center@hinet.net
dateMon, Aug 25, 2008 at 11:37 PM subjectAbuse by user at IP address
118.167.20.180 mailed-bymy_domain
On August 25, 2008, from 08:52:10 am to 08:52:28 am (America/Tijuana time),
user at IP address 118.167.20.180 abused <my> web site with the below
referenced offending code (relevant web server log section is attached and
named as abuse-118_167_20_180.txt).
Return-Path: <my_email_address>
Received: from localhost (localhost [127.0.0.1])
by dns.adsl.hinet.net (8.12.3/8.12.3/Debian-6.6) with ESMTP id
m7QA4XUN014545
for <cracker@localhost>; Tue, 26 Aug 2008 18:06:31 +0800
[...]
----------End of unformatted
reply----------------------------------------------------------
The above was attached to the formated email reply below:
from cracker@hinet.net to<my_email_address>
dateTue, Aug 26, 2008 at 4:24 AM subject[HiNetSOC/Craker : 1219749049]HiNet
Notification(HiNet 通知) mailed-bylcss.hinet.net
hide details 4:24 AM (11 hours ago)
Reply
Dear Sir:
Thank you for your email. Please kindly provide us more detail information
about the bad behavior at least including the attackers' IP address, time
(GMT, Greenwich Mean Time) and evidence for further processing.
- Hide quoted text -
------End of formatted email
reply-------------------------------------------------------------------
No wonder spam and intrusion attempts never end.
Jose R R
http://www.metztli-it.com
IBM Lotus Symphony <http://symphony.lotus.com> is officially supported on RH
and SuSE; official Ubuntu support coming at the end of August 2008.
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
08-27-2008, 11:41 AM
"Burke, Thomas G."
Infiltration of ISP providers by crackers.
Personally, I just blocked all of apnic... They're the source of over 90% of my issues, and I don't really care if I make them mad.
Of course, youmight not be able to do that if you're running a business...
-----Original Message-----
From: redhat-list-bounces@redhat.com [mailto:redhat-list-bounces@redhat.com] On Behalf Of Jose R R
Sent: Wednesday, August 27, 2008 12:05 AM
To: General Red Hat Linux discussion list
Subject: Infiltration of ISP providers by crackers.
So ...(sigh) what do you do when you complain to a given ISP provider about a case of attempted abuse by one of their IP addresses and you get a response from someone in the "security team" whose email name is "cracker?"
Apparently some (or many) of these crackers own (with their consent or not) even their ISP providers --or worse, some (or many) ISP providers may be crackers themselves!
A portion of my original complaint to the ISP --where I list one of the attempted abuse records by the cracker for informational purposes:
----------------------------------------------------------------------------------
from myself <my_emai_address> tonetwork-adm@hinet.net, network-center@hinet.net dateMon, Aug 25, 2008 at 11:37 PM subjectAbuse by user at IP address 118.167.20.180 mailed-bymy_domain
On August 25, 2008, from 08:52:10 am to 08:52:28 am (America/Tijuana time), user at IP address 118.167.20.180 abused <my> web site with the below referenced offending code (relevant web server log section is attached and named as abuse-118_167_20_180.txt).
Return-Path: <my_email_address>
Received: from localhost (localhost [127.0.0.1])
by dns.adsl.hinet.net (8.12.3/8.12.3/Debian-6.6) with ESMTP id
m7QA4XUN014545
for <cracker@localhost>; Tue, 26 Aug 2008 18:06:31 +0800 [...]
----------End of unformatted
reply----------------------------------------------------------
The above was attached to the formated email reply below:
from cracker@hinet.net to<my_email_address> dateTue, Aug 26, 2008 at 4:24 AM subject[HiNetSOC/Craker : 1219749049]HiNet Notification(HiNet 通知) mailed-bylcss.hinet.net hide details 4:24 AM (11 hours ago) Reply
Dear Sir:
Thank you for your email. Please kindly provide us more detail information about the bad behavior at least including the attackers' IP address, time (GMT, Greenwich Mean Time) and evidence for further processing.
- Hide quoted text -
------End of formatted email
reply-------------------------------------------------------------------
No wonder spam and intrusion attempts never end.
Jose R R
http://www.metztli-it.com
IBM Lotus Symphony <http://symphony.lotus.com> is officially supported on RH and SuSE; official Ubuntu support coming at the end of August 2008.
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
08-27-2008, 11:52 AM
George Magklaras
Infiltration of ISP providers by crackers.
I do not normally bother following up on reports on all attacks. Most of
them are scripted and there are too many. So, my IPS/IDS has a good list
of 'not-to-block' IP addresses and whatever else outside this IP list
attacks any service is blocked. Most good IPS/IDS vendors also provide
near real-time lists of network blocks, especially from countries with
large ISP segments that typically consist of various classes of IP
blocks for home DSL/dialup customers, where most of the compromised PCs
serve botnets and malicious scripters. This keeps the number of IPTABLES
rules down and can block most of these annoying attacks.
GEO-IP blocking may also help if you definitely know that you should not
be expecting traffic from any part of the world. Problem is you need to
update the ip list regularly and be ready to accept some false positives
from IPs that suddenly are legit.
For other types of more persistent and unusual attacks, you need to get
in touch with the CERT team of a major telco provider. They are keen to
know of these issues and if they provide the backbone of your
connectivity, maybe there is part of your SLA that covers these sort of
things, generally speaking.
GM
--
--
George Magklaras
Senior Computer Systems Engineer/UNIX Systems Administrator
EMBnet Technical Management Board
The Biotechnology Centre of Oslo,
University of Oslo
http://folk.uio.no/georgios
Jose R R wrote:
So ...(sigh) what do you do when you complain to a given ISP provider about
a case of attempted abuse by one of their IP addresses and you get a
response from someone in the "security team" whose email name is "cracker?"
Apparently some (or many) of these crackers own (with their consent or not)
even their ISP providers --or worse, some (or many) ISP providers may be
crackers themselves!
A portion of my original complaint to the ISP --where I list one of the
attempted abuse records by the cracker for informational purposes:
----------------------------------------------------------------------------------
from myself <my_emai_address> tonetwork-adm@hinet.net,
network-center@hinet.net
dateMon, Aug 25, 2008 at 11:37 PM subjectAbuse by user at IP address
118.167.20.180 mailed-bymy_domain
On August 25, 2008, from 08:52:10 am to 08:52:28 am (America/Tijuana time),
user at IP address 118.167.20.180 abused <my> web site with the below
referenced offending code (relevant web server log section is attached and
named as abuse-118_167_20_180.txt).
Return-Path: <my_email_address>
Received: from localhost (localhost [127.0.0.1])
by dns.adsl.hinet.net (8.12.3/8.12.3/Debian-6.6) with ESMTP id
m7QA4XUN014545
for <cracker@localhost>; Tue, 26 Aug 2008 18:06:31 +0800
[...]
----------End of unformatted
reply----------------------------------------------------------
The above was attached to the formated email reply below:
from cracker@hinet.net to<my_email_address>
dateTue, Aug 26, 2008 at 4:24 AM subject[HiNetSOC/Craker : 1219749049]HiNet
Notification(HiNet 通知) mailed-bylcss.hinet.net
hide details 4:24 AM (11 hours ago)
Reply
Dear Sir:
Thank you for your email. Please kindly provide us more detail information
about the bad behavior at least including the attackers' IP address, time
(GMT, Greenwich Mean Time) and evidence for further processing.
- Hide quoted text -
------End of formatted email
reply-------------------------------------------------------------------
No wonder spam and intrusion attempts never end.
Jose R R
http://www.metztli-it.com
IBM Lotus Symphony <http://symphony.lotus.com> is officially supported on RH
and SuSE; official Ubuntu support coming at the end of August 2008.
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
08-28-2008, 03:05 AM
"Jose R R"
Infiltration of ISP providers by crackers.
>
> On Wed, Aug 27, 2008 at 4:41 AM, Burke, Thomas G. <tg.burke@ngc.com>wrote:
>> Personally, I just blocked all of apnic... They're the source of over 90%
>> of my issues, and I don't really care if I make them mad.
>>
>
On Wed, Aug 27, 2008 at 4:52 AM, George Magklaras <georgios@biotek.uio.no>wrote:
> I do not normally bother following up on reports on all attacks. Most of
> them are scripted and there are too many. So, my IPS/IDS has a good list of
> 'not-to-block' IP addresses and whatever else outside this IP list attacks
> any service is blocked. Most good IPS/IDS vendors also provide near
> real-time lists of network blocks, especially from countries with large ISP
> segments that typically consist of various classes of IP blocks for home
> DSL/dialup customers, where most of the compromised PCs serve botnets and
> malicious scripters. This keeps the number of IPTABLES rules down and can
> block most of these annoying attacks.
>
> GEO-IP blocking may also help if you definitely know that you should not be
> expecting traffic from any part of the world. Problem is you need to update
> the ip list regularly and be ready to accept some false positives from IPs
> that suddenly are legit.
>
> For other types of more persistent and unusual attacks, you need to get in
> touch with the CERT team of a major telco provider. They are keen to know of
> these issues and if they provide the backbone of your connectivity, maybe
> there is part of your SLA that covers these sort of things, generally
> speaking.
>
Your insights and suggestions are appreciated, thank you.
Jose R R
http://www.metztli-it.com
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
Infiltration of ISP providers by crackers.
