Malicious Code in input-error-field (npm)

input-error-field Updated 02 Oct 2025

Summary

25/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8617: Malicious code in input-error-field (npm). Affects input-error-field versions 3.7.14. 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 'input-error-field' package is an npm package that is used for handling input errors in web forms. It provides functionality to display error messages and highlight input fields with errors. The package is commonly used in web development projects to improve the user experience by providing clear feedback on form validation errors. However, a specific version of this package, 3.7.14, has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The malicious code in the 'input-error-field' package communicates with a domain associated with malicious activity. This can have serious ramifications for applications that use this package, as the malicious code can potentially compromise user data, inject additional malicious code, or perform other unauthorized actions. It is crucial to identify and address this vulnerability to ensure the security and integrity of the affected applications.

How To Fix

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

npm uninstall input-error-field

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

There is no specific workaround mentioned for this vulnerability. The best course of action is to follow the steps mentioned in the 'how_to_fix' section and remove the affected version of the package.

Conclusion

The 'input-error-field' package version 3.7.14 has been identified as malicious. It is crucial to remove this version from your project and update to a non-malicious version to ensure the security and integrity of your application. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for input-error-field →

Share this vulnerability

FAQ

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will analyze it for any open-source vulnerabilities, including this one.

The malicious code in the 'input-error-field' package can lead to unauthorized access to user data, injection of additional malicious code, and other security breaches. This can result in compromised user privacy, data loss, and potential legal and reputational consequences for affected applications.

While specific exploits targeting this vulnerability have not been mentioned, it is important to address the issue promptly as the malicious code can be leveraged by attackers to carry out various malicious activities. It is always recommended to stay updated with the latest security patches and fixes.

Yes, there are several alternative packages available for handling input errors in web forms. Some popular options include 'formik', 'react-hook-form', and 'redux-form'. It is recommended to thoroughly evaluate and test alternative packages before integrating them into your project.

To prevent similar vulnerabilities in the future, it is important to regularly update and review the dependencies used in your project. Stay informed about security advisories and vulnerability reports related to the packages you rely on. Additionally, consider using automated vulnerability monitoring tools like Vulert (https://vulert.com) to receive real-time alerts and ensure timely mitigation of vulnerabilities.

How To Fix

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

npm uninstall input-error-field

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