This IP address has been reported a total of
17
times from
11 distinct
sources.
193.239.154.101 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
Wazuh Alert Evidence: Jun 06 19:58:23 pico-gw1 postfix/smtpd[3927956]: NOQUEUE: reject: RCPT from un ...
show moreWazuh Alert Evidence: Jun 06 19:58:23 pico-gw1 postfix/smtpd[3927956]: NOQUEUE: reject: RCPT from unknown[193.239.154.101]: 554 5.7.1 Service unavailable; Client host [193.239.154.101] blocked using bl.spamcop.net; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<st56500-niigata280.niigata.bbiq.jp>
show less
Source of spoofed email forging From: @atsoho.com domain. Observed via aggregated DMARC RUA reports. ...
show moreSource of spoofed email forging From: @atsoho.com domain. Observed via aggregated DMARC RUA reports.
Between 2026-05-13 and 2026-05-17, this IP and 250+ neighbors in 193.239.154.0/24 (AS136038 HDTIDC LIMITED / AS136526 ALLCLOUD LIMITED) sent over 11,000 spoofed emails forging the From header as our domain "atsoho.com".
All messages fail SPF and DKIM authentication against atsoho.com (DMARC enforced: p=quarantine). Legitimate atsoho.com mail is sent exclusively from Google Workspace, SocketLabs, and XServer.
Reporting receivers (sample): Mail.Ru, Microsoft (Enterprise Outlook), seznam.cz, JCOM, au.com, Yahoo, GMO Pepabo, GMO Internet.
WHOIS abuse-mailbox ([email protected]) is non-functional (550 5.1.1 rejection). APNIC and RIPE NCC have been notified of the invalid abuse contact.
show less
Dec 8 22:46:56 server postfix/smtpd[3471959]: connect from unknown[193.239.154.101]
Dec 8 22:46:57 ...
show moreDec 8 22:46:56 server postfix/smtpd[3471959]: connect from unknown[193.239.154.101]
Dec 8 22:46:57 server postfix/smtpd[3471959]: NOQUEUE: reject: RCPT from unknown[193.239.154.101]: 554 5.7.1 Service unavailable; Client host [193.239.154.101] blocked using zen.spamhaus.org; Listed by SBL, see https://check.spamhaus.org/sbl/query/SBL520298 / Listed by DROP, see https://check.spamhaus.org/sbl/query/SBL520298 / Listed by CSS, see https://check.spamhaus.org/query/ip/193.239.154.101 / Listed by XBL, see https://check.spamhaus.org/query/ip/193.239.154.101; from=<> to=<[email protected]> proto=ESMTP helo=<C202512051862047.local>
...
show less
Nov 23 01:09:03 server postfix/smtpd[3586288]: connect from unknown[193.239.154.101]
Nov 23 01:09:04 ...
show moreNov 23 01:09:03 server postfix/smtpd[3586288]: connect from unknown[193.239.154.101]
Nov 23 01:09:04 server postfix/smtpd[3586288]: NOQUEUE: reject: RCPT from unknown[193.239.154.101]: 554 5.7.1 Service unavailable; Client host [193.239.154.101] blocked using zen.spamhaus.org; Listed by XBL, see https://check.spamhaus.org/query/ip/193.239.154.101 / Listed by SBL, see https://check.spamhaus.org/sbl/query/SBL520298 / Listed by DROP, see https://check.spamhaus.org/sbl/query/SBL520298 / Listed by CSS, see https://check.spamhaus.org/query/ip/193.239.154.101; from=<> to=<[email protected]> proto=ESMTP helo=<C202511200058461.local>
...
show less
Nov 22 11:49:18 server postfix/smtpd[3425208]: connect from unknown[193.239.154.101]
Nov 22 11:49:18 ...
show moreNov 22 11:49:18 server postfix/smtpd[3425208]: connect from unknown[193.239.154.101]
Nov 22 11:49:18 server postfix/smtpd[3425208]: NOQUEUE: reject: RCPT from unknown[193.239.154.101]: 554 5.7.1 Service unavailable; Client host [193.239.154.101] blocked using zen.spamhaus.org; Listed by DROP, see https://check.spamhaus.org/sbl/query/SBL520298 / Listed by CSS, see https://check.spamhaus.org/query/ip/193.239.154.101 / Listed by XBL, see https://check.spamhaus.org/query/ip/193.239.154.101 / Listed by SBL, see https://check.spamhaus.org/sbl/query/SBL520298; from=<> to=<[email protected]> proto=ESMTP helo=<C202511200058461.local>
...
show less