Critical Malicious Code Vulnerability in secp256 Package

secp256 Updated 20 Feb 2026

Summary

20/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-970: Malicious code in secp256 (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 secp256 package is a cryptographic library used in various applications for secure key generation and management. It is designed to facilitate elliptic curve cryptography, providing developers with tools to implement secure communications. However, the package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the secp256 package, identified by the alias GHSA-p683-99hw-p2fq. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of this code poses a significant threat, as it may not only affect the immediate application but also lead to broader security breaches across systems that rely on this package.

How To Fix

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

npm uninstall secp256

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 measure, avoid using the secp256 package in your applications until the issue is resolved. If you must continue development, consider using alternative cryptographic libraries that do not have known vulnerabilities.

Conclusion

The secp256 package has been identified as containing malicious code, posing a significant security risk to any systems using it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your software dependencies.

See every vulnerability recorded for secp256 →

Share this vulnerability

FAQ

Immediately remove the secp256 package from your system and rotate any secrets or keys stored on that computer.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code or installation.

Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and loss of control over your systems.

The best mitigation is to remove the package entirely and use alternative libraries until a secure version is released.

Utilize tools like Vulert to monitor your dependencies for vulnerabilities and receive alerts in real-time.

How To Fix

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

npm uninstall secp256

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