Walter.Net.HoneyPot 2022.12.14.648

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
.NET 6.0
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Walter.Net.HoneyPot --version 2022.12.14.648
NuGet\Install-Package Walter.Net.HoneyPot -Version 2022.12.14.648
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Walter.Net.HoneyPot" Version="2022.12.14.648" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Walter.Net.HoneyPot --version 2022.12.14.648
#r "nuget: Walter.Net.HoneyPot, 2022.12.14.648"
#r directive can be used in F# Interactive and Polyglot Notebooks. 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.12.14.648

// Install Walter.Net.HoneyPot as a Cake Tool
#tool nuget:?package=Walter.Net.HoneyPot&version=2022.12.14.648

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 Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
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
2023.11.13.1117 1,490 11/13/2023
2023.10.26.1502 1,428 10/29/2023
2023.10.12.1926 1,572 10/12/2023
2023.9.14.812 1,697 9/14/2023
2023.9.7.1748 1,714 9/7/2023
2023.9.7.1241 1,681 9/7/2023
2023.9.6.1001 1,658 9/6/2023
2023.9.5.1246 1,694 9/5/2023
2023.9.5.1032 1,665 9/5/2023
2023.8.31.1522 1,732 8/31/2023
2023.8.29.1040 1,737 8/29/2023
2023.8.17.901 1,796 8/17/2023
2023.8.9.1314 1,906 8/9/2023
2023.8.2.750 1,992 8/2/2023
2023.7.12.830 1,960 7/12/2023
2023.7.5.1419 2,047 7/6/2023
2023.6.14.1628 2,080 6/14/2023
2023.6.11.1304 2,198 6/11/2023
2023.5.30.1640 2,116 5/30/2023
2023.5.4.1552 2,231 5/4/2023
2023.5.1.1524 2,170 5/1/2023
2023.4.29.910 2,373 4/29/2023
2023.4.12.1236 2,392 4/12/2023
2023.3.22.1456 2,508 3/22/2023
2023.3.14.1356 2,631 3/14/2023
2023.3.1.810 2,647 3/1/2023
2023.2.25.11857 2,658 2/25/2023
2023.2.22.27 2,673 2/22/2023
2023.2.15.1413 2,725 2/15/2023
2023.2.11.1628 2,778 2/11/2023
2023.1.11.534 2,914 1/11/2023
2022.12.30.711 2,988 12/30/2022
2022.12.16.1536 930 12/16/2022
2022.12.15.1241 874 12/16/2022
2022.12.15.1108 2,991 12/15/2022
2022.12.14.648 3,066 12/14/2022
2022.11.27.1059 3,092 11/27/2022
2022.11.21.338 3,160 11/21/2022
2022.11.14.1819 3,266 11/14/2022
2022.11.13.917 3,225 11/13/2022
2022.11.7.1632 982 11/13/2022
2022.10.31.740 5,809 11/1/2022
2022.10.15.652 6,329 10/15/2022
2022.10.1.810 6,620 10/1/2022
2022.9.26.1444 6,696 9/26/2022
2022.9.14.1508 6,768 9/14/2022
2022.9.14.809 6,870 9/14/2022
2022.9.8.1009 7,001 9/8/2022
2022.8.20.1007 6,897 8/20/2022
2022.8.1.1 7,020 7/31/2022
2022.7.1300 7,188 7/1/2022
2022.7.31.1016 7,098 7/31/2022
2022.7.15.841 7,099 7/15/2022
2022.6.21.647 7,075 6/21/2022
2022.5.18.638 7,133 5/19/2022
2022.5.16.853 7,225 5/19/2022
2022.5.16.816 7,174 5/16/2022
2022.5.4.1010 7,133 5/4/2022
2022.4.10.947 7,686 4/10/2022
2022.4.10.925 7,606 4/10/2022
2022.4.10.828 7,593 4/10/2022
2022.4.1.1545 7,777 4/1/2022
2022.3.31.823 6,683 3/31/2022
2022.3.26.1103 7,813 3/26/2022
2022.3.26.820 7,419 3/26/2022
2022.3.25.840 6,879 3/26/2022
2022.3.24.1701 1,199 3/25/2022
2022.2.16.1131 8,020 2/17/2022
2022.2.16.834 7,763 2/17/2022
2022.2.15.824 2,102 2/17/2022
2022.2.11.1452 2,205 2/17/2022
2022.2.11.931 2,014 2/17/2022
2022.2.5.1114 8,094 2/5/2022
2022.1.17.1158 7,850 1/17/2022
2022.1.10.1505 8,258 1/10/2022
2022.1.10.537 8,213 1/10/2022
2022.1.5.1139 7,674 1/8/2022
2021.12.28.1452 8,748 12/28/2021
2021.12.16.812 8,330 12/16/2021
2021.11.23.1528 14,560 11/24/2021
2021.11.21.925 14,449 11/22/2021
2021.11.19.1503 979 11/22/2021
2021.11.19.847 9,475 11/19/2021
2021.11.18.1824 8,900 11/16/2021
2021.11.10.852 9,677 11/10/2021
2021.11.9.2021 9,198 11/9/2021
2021.11.8.2109 6,933 11/9/2021
2021.11.8.1612 7,518 11/8/2021
2021.11.7.1021 7,601 11/8/2021
2021.11.3.1612 7,875 11/4/2021
2021.11.1.1102 6,365 11/1/2021
2021.10.25.1206 7,902 10/25/2021
2021.10.23.1310 7,783 10/25/2021
2021.10.19.1522 7,808 10/19/2021
2021.10.16.1325 7,646 10/18/2021
2021.10.6.1546 7,729 10/6/2021
2021.10.5.1450 7,923 10/5/2021
2021.10.4.1155 7,940 10/5/2021
2021.10.4.807 1,048 10/5/2021
2021.10.1.753 7,960 10/1/2021
2021.9.27.1005 7,377 9/28/2021
2021.9.26.1913 7,995 9/26/2021
2021.9.19.1015 7,634 9/19/2021
2021.9.17.1702 4,600 9/17/2021
2021.9.17.1449 10,445 9/17/2021
2021.9.13.1600 5,902 9/13/2021
2021.9.12.1100 4,362 9/13/2021
2021.9.11.2004 7,250 9/11/2021
2021.9.9.1110 7,701 9/9/2021
2021.9.7.1901 7,848 9/8/2021
2021.9.7.1121 7,966 9/7/2021
2021.9.7.927 1,022 9/7/2021
2021.9.6.1518 7,419 9/7/2021
2021.9.4.1124 7,784 9/4/2021
2021.9.2.708 7,495 9/4/2021
2021.9.0.1259 7,437 9/2/2021
2021.8.2200 6,902 8/23/2021
2021.8.2100 7,751 8/23/2021
2021.8.22.900 7,948 8/22/2021
2021.8.18.1500 7,847 8/18/2021
2021.8.18.930 7,814 8/18/2021
2021.8.14.1600 7,822 8/16/2021
2021.8.14.829 3,742 8/14/2021
2021.8.9.1105 7,851 8/9/2021
2021.8.8.1612 7,528 8/8/2021
2021.8.8.1138 6,845 8/8/2021
2021.8.6.1044 7,560 8/6/2021
2021.8.4.1355 8,161 8/5/2021
2021.7.30.2118 8,043 7/31/2021
2021.7.27.926 8,005 7/28/2021
2021.7.23.931 8,088 7/26/2021
2021.7.22.1456 7,705 7/23/2021
2021.7.15.1547 7,773 7/15/2021
2021.7.13.812 7,640 7/13/2021
2021.7.8.1527 7,937 7/10/2021
2021.7.5.1649 6,946 7/5/2021
2021.6.29.1453 8,103 6/30/2021
2021.6.26.1753 8,378 6/27/2021
2021.6.25.1849 7,990 6/25/2021
2021.6.24.1518 7,976 6/24/2021
2021.6.20.729 15,248 6/20/2021
2021.6.14.2025 8,109 6/15/2021
2021.6.13.2035 8,477 6/14/2021
2021.6.12.1154 7,839 6/13/2021
2021.6.9.1120 8,099 6/9/2021
2021.6.7.2103 1,047 6/7/2021
2021.6.3.1509 7,791 6/3/2021
2021.5.31.1533 8,031 5/31/2021
2021.5.31.1415 8,022 5/31/2021
2021.5.25.1732 7,019 5/25/2021
2021.5.24.1128 7,748 5/24/2021
2021.5.24.1019 7,635 5/24/2021
2021.5.12.1054 7,643 5/12/2021
2021.5.12.637 6,013 5/12/2021
2021.5.10.1442 7,082 5/11/2021
2021.5.8.1226 7,574 5/8/2021

Major releases that add functionality other than optimization and minor bug fixing
14 December 2022
- Update to .Net SDK 3.1.426, 6.0.404 and 7.0.101


7 December 2022
- re-enable support for .net standard 2.1

21 November 2022
- Update to integrate the .net 7.0 cypher package release
- Update package references

14 November 2022
- Update NuGet Packages

6 November 2022
- Add support for .Net 7

15 November 2022
- Update NuGet package references


1 October 2022
- Update build with new SDK
- Update code sign certificates

14 September 2022
- Update to include new package 6.0.X and Microsoft CVE-2022-38013

02 September 2022
- Please make sure to update servers using this packages due to a security bug in .net
 > System.Security.Cryptography.Xml      4.5.0      Moderate   https://github.com/advisories/GHSA-2m65-m22p-9wjw
     > System.Text.Encodings.Web             4.5.0      Critical   https://github.com/advisories/GHSA-ghhp-997w-qr28

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