Not intentionally malware. But the OPAM install [0] deleted my $PATH, and it took me a while how to fix that one. They've since fixed what allowed the problem

Not intentionally malware. But the OPAM install [0] deleted my $PATH, and it took me a while how to fix that one. They've since fixed what allowed the problem to happen [1], well it was a combination of that (normal shell problems) and a power-outage that killed the installer just before completion (in which case the script may just think it's complete). But I'm sure similar catastrophic side-effects can occur in other install scripts out there. [0] https://opam.ocaml.org/doc/Install.html https://opam.ocaml.org/doc/Install.html [1] https://github.com/ocaml/opam/issues/2165 https://github.com/ocaml/opam/issues/2165