Compromised printer?

Turns out that an employee ran an NMAP scan to discover some devices. Apparently this can cause an unexpected print (???). Below from the Meraki forum:

*Look what I found. I am going to try this on some of my printers: https://github.com/nmap/nmap/issues/2237

Describe the bug Aggressive option '-A' on printers produce unwanted print : binary blob with 'random1random2...'. The printed payload 'random1random2...' is located here : "/usr/share/nmap/nselib/shortport.lua" line 261 To Reproduce Run the following command on a printer device : nmap -A X.X.X.34 -vvvvvvvvv -p 9100 --script-trace*

Kudos to Meraki Community member Brandon S