One common antipattern in software engineering is the Antipattern Antipattern:
Thinking that the term "antipattern" means "never use this pattern."
"An antipattern is just like a pattern, except that instead of a solution it gives something that looks superficially like a solution, but isn't one." Andrew Koenig, Journal of Object-Oriented Programming, April 1995
Antipatterns are disguised as good solutions. The danger is when the pattern is applied without evaluation the alternatives. Antipatterns become antipatterns when:
The patterns results in unintended and undesired outcomes and another pattern exists that is a repeatable and effective solution.
That means that antipatterns are context-dependent. Antipatterns can be the best solution when other patterns do not exist or are not effective solutions. The context of the problem you want to solve and the system you are working in can change an antipattern into a pattern.
So, what's the fix to the Antipattern Antipattern?
Understanding that more often than not the antipattern will not be the solution you want. But if the evaluated alternatives are not effective, the antipattern can be used with the knowledge of the potential desired and undesired outcomes.