Speaking as someone who owned a Commodore PET, knew others who owned them, occasionally worked at a sort of "pre-Internet Internet cafe" with dozens of PETs available for public use, and who sold a Commodore PET into the used market during their heyday, no.
PET's were pre-consumer-Internet and pre-BBS, so if someone was in a position to damage your machine, they were there in the room with you. There was no risk of random network viruses.
Sneaker-net sharing of programs on cassette tapes made tape-borne viruses impractical, to say nothing of their likely not even having been invented yet.
People did not set their friends' machines on fire, either digitally or with matches.
The one thing I liked about the PET was that it had a really cool set of graphic characters in the high bit character range.
Interestingly, it seems some people have also tried to inhibit the CRTC vsync signal and create their own with a similar trick to the PET POKE - see 7.3 on page 40: https://shaker.logonsystem.eu/ACCC1.7-EN.pdf (and a comment on page 41 that they have seen damaged chips resulting from this - the PPI is the 8255 bi-directional parallel port driver chip, used on the Amstrad for scanning keyboard, driving the sound chip and miscellaneous such as the VSYNC line).
I don't remember people talking a lot about it, but it was widely known. The only time I ever heard it being brought up was as a counterexample to the assertion that "you can't actually break a computer by typing the wrong thing at the keyboard". That was said a lot to reassure normal people who were afraid to touch computer keyboards out of fear of breaking expensive equipment.
In practice, the "killer poke" didn't really live up to its name. What it did was set the monitor sync rate to something the monitor couldn't handle. That would eventually damage the monitor, but you had to let it sit in that state for a long time (putting up with the terrible squeal it caused) for that to happen.
I took it more as a kind of lesson that software could sometimes break out of the normal execution model it runs in, sometimes in very unexpected ways and with possibly significant consequences. (I was just a kid, so probably my mother lead me there. She was an experienced systems architect, or whatever they called it at the time, and had plenty of practical experience with machines that were a lot more raw than the PET.)
I liked the PET, and while it had a better basic, monitor, and character set, it was lacking a graphics capability like the Apple ][. That’s what reduced PET sales. E.g., a C64 was basically a PET plus graphics & sound (w/enough memory to use them) and sold like gangbusters.
On middle generation PETs - the dynamic RAM, pre-6845, small screen ones, the POKE did nothing.
It was the later, big screen PETs - both 40 and 80 column - that were vulnerable. It seems the POKE - which set an input pin to output - actually prevented the vertical deflection from operating. I can see that frying something if left on for a while.
This is all from memory so some of the details may be wrong. It was known, but not considered a big deal. But were there a lot of consumer sales of PETs anyway? They seemed to be more of an institutional (school) machine. Consumers really got into it with the VIC20 and of course the C64 later.
By the time the Apple IIe, Commodore-64 and IBM PC came out, they were just a lot better and/or cheaper and that's what really killed the PET..
POKE 59458,62
At least that's what I remember. I didn't check first.