International Revenue Share Fraud (IRSF)

54 pointsposted 5 hours ago
by djkurlander

18 Comments

sciencejerk

4 hours ago

Thanks for sharing your interesting research! Can you explain your honeypotting approach further? How are you "presenting" as a SIP relay? What other honeypots or protocols can you detect?

djkurlander

4 hours ago

I set up servers on the net that masquerade as a SIP relay by essentially supporting the protocol but with few authentication protections. Malware bots scan the IPv4 space looking for such machines that they can use as a relay. My honeypot is actually an extensible framework, and we also can mimic SSH, Telnet, HTTP, SMB, FTP, RDP, SMTP, MQTT, Node-Red, MODB, S7, and SNMP. Individual servers can easily be set up to scan any subset of those. Check out https://knock-knock.net to get a visual sense of what the honeypot is doing!

Oarch

4 hours ago

Hell of an opening on this blog post. Solid write up! Glad honeypots like this exist.

djkurlander

4 hours ago

Much appreciated! Trying to help out the community with the honeypot & API, and it's always fascinating what attack patterns show up.

richwater

4 hours ago

This is quite the claim (and I'm not saying you are wrong from making it).

I just would have expected some of these institutions to be better.

djkurlander

4 hours ago

Yes - I would have expected better from these institutions as well, but there's always going to be someone who brings their rogue laptop onto the corporate net. The key is how fast the security catches it. They can use the api that I describe in the blog to check my honeypot for their IPs. Very simple to put into a daily or hourly script.

djkurlander

5 hours ago

[flagged]

saaaaaam

4 hours ago

"Coordinated attack" might raise more than eyebrows with the legal departments of the companies you've called out.

>Over the next 27 hours, in four distinct waves, all of them tried to use my VoIP (SIP) server to place phone calls on my dime.

As you've clarified in your comment here the companies did not do this. Compromised machines on their networks, controlled by third parties did it.

djkurlander

4 hours ago

The actual blog post clarifies this as well. But still in some sense these organizations share some level of responsibility if it is their machines, attacking from their ASN.

saaaaaam

4 hours ago

Did you use AI to write the blog post?

djkurlander

4 hours ago

Wrote the blog post myself, and used AI to clear up typos and occasionally improve wording. I have a PhD in computer science, but I was initially planning to pursue journalism instead, so I like to think that I can write good :-).

mikeaskew4

4 hours ago

No comments, but thank you for sharing and staying vigilant.

djkurlander

4 hours ago

Thanks! Just trying to keep the world safe from marauding Teddy Bears.

Tiberium

4 hours ago

A question: why are you writing this with an LLM? Can you not write with your own words, at least on HN?

djkurlander

4 hours ago

As mentioned above, wrote the blog post myself and had AI proofread and edit. As for the honeypot itself, I'm a greybeard computer scientist, and I architected the system very deliberately myself, using AI as a coding accelerator. Earlier in my career, moving from Assembly to C, I certainly appreciated the convenience of a higher level language. Same from C to C++ to Java/Lisp/Python to LLM. It's always a march to higher level languages and letting the computer do more work.