Malicious Code Detected in erification Package - Security Alert

erification Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19777: Malicious code in erification (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The erification package is an npm module designed for various functionalities within JavaScript applications. It is commonly used for tasks related to user verification processes. However, this package has been found to contain malicious code, posing significant security risks to applications that rely on it. Users of this package should be aware of its vulnerabilities and take immediate action to protect their systems.

Vulnerability Detail

The vulnerability in the erification package stems from the inclusion of malicious code that can compromise the integrity of applications using it. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions. It is crucial for developers to understand the potential ramifications of this vulnerability, as it can severely impact application security and user trust.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall erification

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can prevent the use of the erification package by removing it from your package.json file and running npm install to update your dependencies. Additionally, consider using alternative packages that provide similar functionality without the security risks.

Conclusion

The erification package has been identified as containing malicious code that poses a significant security threat. Developers using this package should take immediate action to remove it and consider alternative solutions to safeguard their applications. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for erification →

Share this vulnerability

FAQ

The erification package is an npm module used for user verification processes in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. It is advisable to remove the package and seek alternatives.

Remove the erification package from your project and replace it with a secure alternative to mitigate security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall erification

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback