ZDF
Sign inSign up

Vulnerabilities

Security incident · MAL-2026-3400

Malicious code in typo-crypto (npm)

Published May 8, 2026 · catalog updated Nov 10, 2026 · Malicious code in typo-crypto

Last checked Nov 10, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-3400. A missing EPSS score is not a low risk. Compare Malicious code in typo-crypto with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Malicious code in typo-crypto).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
npm typo-crypto

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (64edea611ad8e383c09495a7a6f7afd4fb86b88136c331ddf787bf0285259bf3) The package typo-crypto was found to contain malicious code. ## Source: ghsa-malware (cf7e91ea854d018e030bb26d5d7ad3dd10244cab072be91717a499040d16b102) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm typo-crypto4.3.0

How to fix MAL-2026-3400

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for MAL-2026-3400. A missing EPSS score is not a low risk. Compare Malicious code in typo-crypto with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 4.3.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 8, 2026 · GitHub Advisory Database

    Detected

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (64edea611ad8e383c09495a7a6f7afd4fb86b88136c331ddf787bf0285259bf3) The package typo-crypto was found to contain malicious code. ## Source: ghsa-malware (cf7e91ea854d018e030bb26d5d7ad3dd10244cab072be91717a499040d16b102) Any computer that has this package installed or running should be considered fully compromise

  2. Nov 10, 2026 · GitHub Advisory Database

    Updated

    --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (64edea611ad8e383c09495a7a6f7afd4fb86b88136c331ddf787bf0285259bf3) The package typo-crypto was found to contain malicious code. ## Source: ghsa-malware (cf7e91ea854d018e030bb26d5d7ad3dd10244cab072be91717a499040d16b102) Any computer that has this package installed or running should be considered fully compromise

Sources

References

Freshness

Last verified in this catalog Nov 10, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseNov 10, 2026
  • OpenSSF OSV / OSV ScannerNov 10, 2026