Malicious Code Detected in dezporkaimnsfjut Package - Security Alert

dezporkaimnsfjut Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18410: Malicious code in dezporkaimnsfjut (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 package 'dezporkaimnsfjut' is an npm module that is used for various functionalities in JavaScript applications. It may provide utilities or features that developers rely on for building their applications. However, it has been identified to contain malicious code, posing a significant security risk to users who have integrated it into their projects.

Vulnerability Detail

The vulnerability in the 'dezporkaimnsfjut' package originates from the inclusion of malicious code within its source. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The presence of such code is a serious concern for developers and organizations relying on this package for their software solutions.

How To Fix

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

npm uninstall dezporkaimnsfjut

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, consider replacing 'dezporkaimnsfjut' with an alternative package that provides similar functionality without the associated security risks. Review your project's dependencies and ensure that no other malicious packages are included.

Conclusion

The discovery of malicious code in the 'dezporkaimnsfjut' package highlights the importance of maintaining secure coding practices and regularly auditing dependencies. By removing this package and monitoring for vulnerabilities, developers can protect their applications from potential threats.

See every vulnerability recorded for dezporkaimnsfjut →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within your application, potentially leading to data theft or system compromise.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Immediately uninstall the package and review your code for any potential security issues that may have arisen from its use.

Yes, you should look for alternative npm packages that provide similar functionalities but have a good security track record.

Regularly check your dependencies using tools like Vulert, which can alert you in real-time for any open-source vulnerabilities.

How To Fix

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

npm uninstall dezporkaimnsfjut

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