Hi Nico,

Unfortunately, this is my experience from EJPD as well.
Wrong timezones, number-flips and worse.
Luckily with IPv6 often you don’t have a result then because only a tiny fraction of the IP-Space is assigned to active users.
With IPv4... you just don’t know because you do not have the context to evaluate if your disclosure is valid / accurate.
I cannot disclose any details, some (not all!) are rumours anyways and I don’t want to make any sensational claims.
But IMO these BÜPF processes are not handled with the appropriate accuracy and/or technical understanding as they would need to be.

Bottom line: Don’t trust them and only disclose what you are legally obligated to. Especially for follow-ups which looks like guesswork after an obvious wrong inquiry.

Disclaimer: Above information might be wrong or entirely fictional and shall serve for educational purposes only.
None of the information provided can be used in any legal context or be referred to in that regard.
(Nur das nöd no irgendöpper dumm tuät)

br
Simon


From: Nico Schottelius via swinog <swinog@lists.swinog.ch>
Date: Monday, 27 October 2025 at 15:11
To: SwiNOG Mailinglist <swinog@lists.swinog.ch>
Subject: [swinog] Re: Scam request from _ISC-EJPD-UPF-Provid


Update to my own mail, this is so bad I've to share:

- The phone number in the email is just dead. Plain dead.
- Only after sending the email to the swinog list, I got a reply from EJPD
  -> Seems they are reading here more than their own support email
- During the email exchange they insisted that I should "get the
  information" but delayed the answer to WHERE TO FIND it
  though explicity asked
- After I got various private responses to my swinog mail
  I was able to figure out where to login (Swinog is more knowledgable than EJPD)
- After login the IRC page was empty. Clearing the cache, using
  incognito mode, nothing helped. A blank white page.
- Sidenote: Who the F names something in the IT world after Internet relay chat
  (IRC) and deems to be taken serious? What's the next abreviation?
  Authority inquiry aka AI?
- After various further mails, "the IT" fixed the problem and I can see
  the request
- The request is for a phone number
- The worst part: We are not a telco, have   never been a telco nor do
  we ever want to be one.

The sheer incompetence I've witnessed in this exchange is frightening.

So many WTF. Dear EJPD, if you read this, you seriously need to
improve. Your mail and behaviour is matching scammers and amateurs more
than any normal sane authority (aka NSA).

Totally puzzled,

Nico

Nico Schottelius via swinog <swinog@lists.swinog.ch> writes:

> Dear Swinoggers,
>
> we are receiving "Information requests" from a "do not reply" email with
> a footer containing the following the below attached information.
>
> I tried to find out where to login, without success, tried to reach them
> by email, even tried to call. The result is:
>
> - no information on how where any information should be found
> - no response ever to any email (I tried 4x)
>   - Seems like _ISC-EJPD-UPF-Provid@isc-ejpd.admin.ch is a dead dropbox
> - the phone picks up after 4x ringing with a hissing, no person talking
>
> Is this a known scam or is this new scam?
>
> Cheers,
>
> Nico
>
> --------------------------------------------------------------------------------
> From: donotreply@isc-ejpd.admin.ch
> Subject: Reminder: Task Overdue in IRC!
> Date: Mon, 27 Oct 2025 09:00:08 +0100 (CET) (26 minutes, 47 seconds ago)
> Reply-To: donotreply@isc-ejpd.admin.ch
>
> Dear Madam, dear Sir,
>
> The Information Request XXXXX is overdue. Please check your requests in IRC and process it as soon as possible.
> Thank you.
>
> In case of login issues: Please contact the Providermanagement PTSS with your login details
>
>
> Best regards
>
> Post and Telecommunications Surveillance Service PTSS
> Federal Department of Justice and Police FDJP
>
> Eichenweg 3, 3003 Bern
> Phone +41 58 463 34 29
> _ISC-EJPD-UPF-Provid@isc-ejpd.admin.ch
> www.li.admin.ch
> *** This is an automated message. Replies to this email will neither be received nor processed. ***
> --------------------------------------------------------------------------------