weak-password-hashing-anti-pattern

Detect weak password hashing algorithms and recommend bcrypt, Argon2, or scrypt.

8|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/igbuend/grimbard --skill weak-password-hashing-anti-pattern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weak-password-hashing-anti-pattern
Source: https://github.com/igbuend/grimbard/tree/main/skills/weak-password-hashing-anti-pattern
Command: npx skills add https://github.com/igbuend/grimbard --skill weak-password-hashing-anti-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical security vulnerability of weak password hashing, which can lead to mass account compromise through rapid cracking of stored credentials.

Core Features & Use Cases

  • Vulnerability Detection: Identifies the use of outdated or insecure hashing algorithms (MD5, SHA1, unsalted SHA256) for password storage.
  • Secure Hashing Guidance: Recommends and provides examples for using modern, robust algorithms like bcrypt, Argon2, or scrypt with proper salting.
  • Use Case: When reviewing user authentication code, this Skill helps ensure that passwords are not stored in a way that makes them easily crackable by attackers.

Quick Start

Review the current password hashing implementation for security vulnerabilities.

Frequently Asked Questions about weak-password-hashing-anti-pattern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect weak password hashing vulnerabilities in my application code?

Detect weak password hashing by analyzing code for outdated algorithms like MD5, SHA1, or unsalted SHA256. This identifies CWE-327 and CWE-759 vulnerabilities, preventing mass account compromise through easily crackable stored credentials.

Why is using SHA256 without a salt considered a password storage anti-pattern?

Unsalted SHA256 is a password storage anti-pattern because identical passwords produce identical hashes, making them vulnerable to rainbow table attacks. Secure password storage requires algorithms like bcrypt or Argon2 with unique salts to prevent rapid cracking.

What's the best way to securely hash and salt passwords for user authentication?

Securely hash passwords using robust algorithms like bcrypt, Argon2, or scrypt with proper salting. This approach ensures secure password storage and verification, protecting user authentication data from rapid cracking by attackers.

How does Argon2 compare to bcrypt for preventing credential cracking?

Argon2 and bcrypt both provide secure password hashing by incorporating salting and computational cost. Argon2 offers modern memory-hard resistance against specialized cracking hardware, while bcrypt remains a proven standard for secure password storage.

When should I review my password storage implementation for CWE-327 vulnerabilities?

Review password storage implementations for CWE-327 vulnerabilities whenever auditing user authentication code. Checking for insecure hashing algorithms and missing salts ensures credentials are not stored in a way that makes them easily crackable by attackers.