How to fix npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using sha512 in npm

npmINTERMEDIATEMEDIUMUpdated Dec 5, 2025· 418 views

The EINTEGRITY error occurs when npm detects a mismatch between the SHA-512 integrity hash of a downloaded package and the expected hash stored in package-lock.json. npm uses cryptographic hashing to verify that downloaded packages haven't been corrupted or tampered with.

Quick fix

Fixes npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using sha512

npm cache verify
  1. Verify npm cache integrity
  2. Clean npm cache forcefully
  3. Delete lock file and node_modules, then reinstall
  4. Upgrade npm to latest version
npm — error
npm cache verify
npm ERR! code EINTEGRITY
npm ERR! Integrity checksum failed when using sha512

What this error means

The EINTEGRITY error occurs when npm detects a mismatch between the SHA-512 integrity hash of a downloaded package and the expected hash stored in package-lock.json. npm uses cryptographic hashing to verify that downloaded packages haven't been corrupted or tampered with. When the calculated hash doesn't match the stored hash, npm refuses to proceed to protect your system from potentially compromised or corrupted packages. This is a security feature designed to ensure package integrity and detect tampering or corruption during download.

Typical symptoms

  • npm install fails with 'ERR! code EINTEGRITY - Integrity checksum failed when using sha512'
  • Error message shows 'wanted' vs 'got' hash values that don't match
  • Installation stops during dependency resolution
  • Works fine after clearing cache but fails on subsequent installs
  • Issue appears after upgrading npm to a newer version
  • Private/corporate npm registry returns different checksums

Common causes

  1. Corrupted npm cache storing incorrect or partial package files
  2. Network connectivity issues or interruption during download causing partial/corrupted package
  3. package-lock.json contains outdated SHA-1 checksums (npm changed from SHA-1 to SHA-512 in npm v5+)
  4. npm version mismatch - older npm using SHA-1 while package-lock.json expects SHA-512
  5. Private/corporate npm registries or mirrors returning different checksums for same package
  6. HTTP proxies, firewalls, or ISPs interfering with or modifying package downloads
  7. Stale network cache between client and npm registry serving outdated package versions

How to fix "npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using sha512"

1Verify npm cache integrity

Run npm cache verify to check and repair npm's local cache. This command performs garbage collection and verifies the integrity of cached data:

bash
npm cache verify

This works for many users as a quick fix.

2Clean npm cache forcefully

If cache verify doesn't work, force clear the entire npm cache and reinstall:

bash
npm cache clean --force
npm install

This removes all cached packages and downloads fresh copies from the registry.

3Delete lock file and node_modules, then reinstall

Remove both package-lock.json and node_modules directory, clear cache, and run a fresh install:

bash
rm -rf node_modules package-lock.json
npm cache clean --force
npm cache verify
npm install

This regenerates the lock file with current npm checksums and eliminates compatibility issues.

4Upgrade npm to latest version

Update npm itself to the latest version before reinstalling. Newer npm versions have better cache handling:

bash
npm install -g npm@latest
npm install
5Verify your network connection

Check that your internet connection is stable. Try switching networks (e.g., from WiFi to mobile data) to rule out ISP/firewall blocking.

If using a corporate proxy, ensure npm is properly configured:

bash
npm config set proxy http://proxyhost:port
npm config set https-proxy http://proxyhost:port
6Reset npm registry to official source

If you're using a custom or private registry, reset to the official npm registry:

bash
npm config set registry https://registry.npmjs.org/
npm install

This eliminates registry-side checksum issues.

7Try yarn as alternative (last resort)

If all else fails, some users have success switching to yarn, which has different cache and integrity verification mechanisms:

bash
npm install -g yarn
rm -rf node_modules package-lock.json
yarn install

Advanced notes

SHA-1 vs SHA-512 Transition: npm changed its integrity checksum algorithm from SHA-1 to SHA-512 starting with npm v5. If your package-lock.json was generated with an older npm version, it will contain SHA-1 hashes while newer npm expects SHA-512. Regenerating the lock file fixes this.

Private Registry Complications: When using Verdaccio, Artifactory, or other private npm registries/proxies, they may regenerate checksums differently than the public npm registry. Clearing the private registry's cache may be necessary.

Cache Self-Healing: As of npm@5, the npm cache is designed to self-heal from corruption by treating integrity mismatches as cache misses and re-downloading packages.

Corporate Environments: Proxy servers, firewalls, and HTTP interception (SSL inspection) in corporate environments can modify or corrupt packages in transit.

System Clock Issues: Significant system clock skew can cause signature verification to fail. Ensure your system time is synchronized with NTP.

Frequently asked questions

What does "npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using" mean?
json. npm uses cryptographic hashing to verify that downloaded packages haven't been corrupted or tampered with. When the calculated hash doesn't match the stored hash, npm refuses to proceed to protect your system from potentially compromised or corrupted packages.
How do I fix "npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using"?
The EINTEGRITY error occurs when npm detects a mismatch between the SHA-512 integrity hash of a downloaded package and the expected hash stored in package-lock.json. npm uses cryptographic hashing to verify that downloaded packages haven't been corrupted or tampered with.
What causes "npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using"?
Corrupted npm cache storing incorrect or partial package files Network connectivity issues or interruption during download causing partial/corrupted package package-lock.json contains outdated SHA-1 checksums (npm changed from SHA-1 to SHA-512 in npm v5+)
Is the "npm ERR! code EINTEGRITY npm ERR! Integrity checksum failed when using" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading