Walter.Net.HoneyPot 2022.8.1.1 The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved

.NET 5.0 .NET Core 3.1 .NET Standard 2.1
Install-Package Walter.Net.HoneyPot -Version 2022.8.1.1
dotnet add package Walter.Net.HoneyPot --version 2022.8.1.1
<PackageReference Include="Walter.Net.HoneyPot" Version="2022.8.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Walter.Net.HoneyPot --version 2022.8.1.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Walter.Net.HoneyPot, 2022.8.1.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Walter.Net.HoneyPot as a Cake Addin
#addin nuget:?package=Walter.Net.HoneyPot&version=2022.8.1.1

// Install Walter.Net.HoneyPot as a Cake Tool
#tool nuget:?package=Walter.Net.HoneyPot&version=2022.8.1.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

About the Honey-Pot detector

The honey pot detector allows to detect and interact with applications that are attempting to communicate with your server via a particular port. Understanding who is maliciously trying to exploit the system helps identify bad actors and will allow you to tune the system alerting an attempt by a system classified as being a bad actor and will allow the framework to block any requests and or return a payload.

Integrating the honey-pot detector in your application

Integrating the honey-pot listener takes 3 steps.

step 1:

Foreword ports in your edge switch to ports monitored by the honey-pot configuration. A recommendation is to map the ports to a free port not used by the server. An example map port 22 to port 60022 and configure the honey-port to watch any communication on port 4000

step 2

Configure the firewall to allow communication on port 4000.

step 3

Configure the application to subscribe to the port detections. To do this in the firewall you should use a configuration similar to this:

services.AddFireWall()
        .UsePortScannerProtection(connectionString: DatabaseConnections.FireWallState, options =>
               {

                   /* map the service ports to a local port on your computer
                   *  Redirect the requests to your computer and open the firewall 
                   *  for the redirected ports */

                   options.SSH = 4000; // map port 22 to port 4000 on your router 
                   options.TSQL = 4001; // map port 1433 to port 4001 on your router 
                   options.Telnet = 4002; // map port 23 to port 4002 on your router 
                   options.MYSQL = 4005; // map port 3306 to port 4005 on your router
                   options.DNS = 4006; // map port 53 to port 4005 on your router
                   options.Telnet 4007; //map port 23 to port 4007 on your router;

                   /*you can manually map port aliases in the range from 0 till 65535*/
                   options.AddOrUpdate(externalPort: 587, internalPort: 4007, name: "ESMTP Extended Simple Mail Transfer Protocol");
                   options.AddOrUpdate(externalPort: 647, internalPort: 4008, name: "DHCP Fail-over");

                   /*Record up-to 8,000 character when someone is trying to attack the service for legal reporting*/
                   options.MaximumDataSizeToAccept = 254;

                   /*Look between every 100ms and 30000ms if someone is trying to gain access to the system */
                   options.PoolFrequency = 100;

                   /* Add a default reply to any connection, you can send an auto-reply 
                    * You can use the template values:
                    * {IP}  - the attackers IP address
                    * {Port}- the port being attacked
                    * {Name}- the name of the alias being used
                    * {ISP} - the name of the Internet service provider that the attacker is using will be injected
                    * {Country} - the country name will be injected
                    * to personalize the message or leave it blank to record silently*/
                   options.DefaultReply = "This service is being monitored and we have detected your intentions attack {Name}" +
                                          " via {IP}:{Port} to gain unlawful access to the system, please note that any unlawful" +
                                          " activity will be reported to {ISP} as well as the relevant authorities in {Country}";

               })

The above code assumes that you are using the FireWall from NuGet package Walter.Web.FireWall. If you are using any of the services that you are monitoring then map the default ports to custom ports on your router there are 2 steps for this:

  1. Map the custom port on the router, an example map 222 to port 22
  2. Use port 222 to connect using SSH

Please note that a lot of attackers are looking for victims using port scanners to target venerable IP addresses before attacking a system. You can have a look here and see how these attacks are being executed.

Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows
.NET Core netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.1
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Walter.Net.HoneyPot:

Package Downloads
Walter.Web.FireWall The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org.

The application firewall that can be used in .NET 5.0, .Net CORE 3.1 and .NET standard 2.1 applications that would benefit for protection against several types of attacks and is easily activated by service integration. services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your options }); Have a look at the GitHub samples at https://github.com/ASP-WAF/FireWall and https://github.com/ASP-WAF/FireWall/wiki to see how to use the firewall in applications. You can view the firewall in action using https://www.asp-waf.com/Firewall You can get started with the firewall using the samples shown in https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf as well as the on line documentation at https://firewallapi.asp-waf.com/

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2022.8.1.1 162 7/31/2022
2022.7.1300 221 7/1/2022
2022.7.31.1016 147 7/31/2022
2022.7.15.841 162 7/15/2022
2022.6.21.647 248 6/21/2022
2022.5.18.638 347 5/19/2022
2022.5.16.853 349 5/19/2022
2022.5.16.816 416 5/16/2022
2022.5.4.1010 488 5/4/2022
2022.4.10.947 843 4/10/2022
2022.4.10.925 779 4/10/2022
2022.4.10.828 795 4/10/2022
2022.4.1.1545 945 4/1/2022
2022.3.31.823 848 3/31/2022
2022.3.26.1103 938 3/26/2022
2022.3.26.820 843 3/26/2022
2022.3.25.840 847 3/26/2022
2022.3.24.1701 146 3/25/2022
2022.2.16.1131 1,181 2/17/2022
2022.2.16.834 1,132 2/17/2022
2022.2.15.824 275 2/17/2022
2022.2.11.1452 275 2/17/2022
2022.2.11.931 298 2/17/2022
2022.2.5.1114 1,315 2/5/2022
2022.1.17.1158 1,489 1/17/2022
2022.1.10.1505 1,782 1/10/2022
2022.1.10.537 2,144 1/10/2022
2022.1.5.1139 2,049 1/8/2022
2021.12.28.1452 2,804 12/28/2021
2021.12.16.812 3,005 12/16/2021
2021.11.23.1528 9,313 11/24/2021
2021.11.21.925 6,213 11/22/2021
2021.11.19.1503 125 11/22/2021
2021.11.19.847 4,079 11/19/2021
2021.11.18.1824 3,653 11/16/2021
2021.11.10.852 4,759 11/10/2021
2021.11.9.2021 4,258 11/9/2021
2021.11.8.2109 2,371 11/9/2021
2021.11.8.1612 2,830 11/8/2021
2021.11.7.1021 2,855 11/8/2021
2021.11.3.1612 3,231 11/4/2021
2021.11.1.1102 2,492 11/1/2021
2021.10.25.1206 3,304 10/25/2021
2021.10.23.1310 3,127 10/25/2021
2021.10.19.1522 3,198 10/19/2021
2021.10.16.1325 3,131 10/18/2021
2021.10.6.1546 3,235 10/6/2021
2021.10.5.1450 3,470 10/5/2021
2021.10.4.1155 3,085 10/5/2021
2021.10.4.807 243 10/5/2021
2021.10.1.753 3,217 10/1/2021
2021.9.27.1005 2,916 9/28/2021
2021.9.26.1913 3,086 9/26/2021
2021.9.19.1015 2,946 9/19/2021
2021.9.17.1702 1,670 9/17/2021
2021.9.17.1449 4,104 9/17/2021
2021.9.13.1600 2,087 9/13/2021
2021.9.12.1100 1,586 9/13/2021
2021.9.11.2004 3,046 9/11/2021
2021.9.9.1110 3,075 9/9/2021
2021.9.7.1901 3,152 9/8/2021
2021.9.7.1121 3,021 9/7/2021
2021.9.7.927 213 9/7/2021
2021.9.6.1518 2,850 9/7/2021
2021.9.4.1124 3,095 9/4/2021
2021.9.2.708 3,038 9/4/2021
2021.9.0.1259 2,711 9/2/2021
2021.8.2200 2,584 8/23/2021
2021.8.2100 3,109 8/23/2021
2021.8.22.900 3,081 8/22/2021
2021.8.18.1500 3,145 8/18/2021
2021.8.18.930 2,972 8/18/2021
2021.8.14.1600 3,083 8/16/2021
2021.8.14.829 1,366 8/14/2021
2021.8.9.1105 3,124 8/9/2021
2021.8.8.1612 2,926 8/8/2021
2021.8.8.1138 2,656 8/8/2021
2021.8.6.1044 2,966 8/6/2021
2021.8.4.1355 3,290 8/5/2021
2021.7.30.2118 3,231 7/31/2021
2021.7.27.926 2,997 7/28/2021
2021.7.23.931 2,999 7/26/2021
2021.7.22.1456 2,897 7/23/2021
2021.7.15.1547 2,754 7/15/2021
2021.7.13.812 2,954 7/13/2021
2021.7.8.1527 3,106 7/10/2021
2021.7.5.1649 2,628 7/5/2021
2021.6.29.1453 3,158 6/30/2021
2021.6.26.1753 3,446 6/27/2021
2021.6.25.1849 3,131 6/25/2021
2021.6.24.1518 3,010 6/24/2021
2021.6.20.729 6,159 6/20/2021
2021.6.14.2025 3,155 6/15/2021
2021.6.13.2035 3,177 6/14/2021
2021.6.12.1154 3,036 6/13/2021
2021.6.9.1120 3,084 6/9/2021
2021.6.7.2103 235 6/7/2021
2021.6.3.1509 2,872 6/3/2021
2021.5.31.1533 2,976 5/31/2021
2021.5.31.1415 2,857 5/31/2021
2021.5.25.1732 2,504 5/25/2021
2021.5.24.1128 2,844 5/24/2021
2021.5.24.1019 2,893 5/24/2021
2021.5.12.1054 2,528 5/12/2021
2021.5.12.637 1,907 5/12/2021
2021.5.10.1442 2,550 5/11/2021
2021.5.8.1226 2,520 5/8/2021

Major releases that add functionality other than optimization and minor bug fixing
15 June 2022
- Update to support .net 6.0.7 and 3.1.27
- Update package references

21 June 2022
- Update package references
- Update compiler warning

4 May 2022
- Update NuGet References
- Update API definition

15 March 2022
- update to 6.0.3

5 March add base classes used by IDPS framework
- Service discovery updates

24 January 2022
- Add Property monitoring, changing properties at runtime will alter the listening scope and definition
- Allow adding and removing listener while the service is active
- Allow excursive or shared use of ports


16 December 2021
- Update to .Net SDK update 14 December for .NET CORE 3.1.416, and .NET 5.0.404 and 6.0.101

9 November 2021
- Fix package dependency on vulnerable packages from Microsoft by upgrading vulnerable packages

08 November 2021
- Update to .Net NuGet packages .NET 6.0.0, .NET 5.0.403 and core 3.1.415

3 November 2021
- Trigger a on keyword events when a exploit was detected with a given word in the stream send to the socket

2 November 2021
- update port mapping allowing for binding ports from configuration file skipping non-mapped ports with a value of 0

11 October 2021
- CodeSign the binaries as well as the NuGet package for executing in a trust-platform

1 October 2021
- Add additional blocking reason for firewall rule engine to use when getting a port scan or a port exploit in IHoneyPotPortDetection
- Add support for Hex-Dump reading the received data making the data human readable
- Add abstract of the block reason to IHoneyPotPortDetection
- Update capturing missing intercept locations in the report API

26 September 2021
- Update process handling to store actual response not the response template
- Add Date-time stamp for each triggered contact

19 September 2021
- Update NuGet packages release for .Net 5.0.10

4 September 2021
- Add default port configuration for WAC and Tomcat

8 Aug 2021
- update to .NET 6.0 SDK (v6.0.100-preview.6)

30 June 2021
- Add .Net 6.0 binaries to the nuget package

23 June 2021
- Save native attack stream in IHoneyPotPortDetection as Base64 string allowing for attack-replay

15 June 2021
- Update to .Net Core 3.1.17 and .Net 5.0.8 SDK

19 June 2020
- Record data send to the honey-pot based on text encoding detection text

11 June 2021
- Update store GuardResponse in data tables
- Add trace route to detected incident if the option is set

09 June 2021
- Update to .Net SDK 5.0.301 and 3.1.410

07 June 2021
- Update NuGet Package references

31 May 2021
- Update to more efficiently extract WHOIS data for more possible attackers

12 April 2021
- Update to new code base after .net security violation fix

10 May 2021
- Update Database based storage

05 April 2021
- Update process data processing
- Log requests that do not send data

22 March 2021 - performance update
- Logging update