Critical Malicious Code Vulnerability in application-phskck Package

application-phskck Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190502: Malicious code in application-phskck (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The application-phskck package is an npm module designed for specific functionalities within JavaScript applications. It is utilized by developers to streamline certain processes in their projects. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the discovery of embedded malicious code within the application-phskck package. This code can compromise any computer that has the package installed, leading to unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code categorizes it under CWE-506, indicating that it contains code that appears to be harmful. Systems running this package should be considered fully compromised, and there is no guarantee that simply removing the package will eliminate all traces of the malicious software.

How To Fix

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

npm uninstall application-phskck

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 workaround, it is recommended to isolate the affected system from the network and perform a thorough security audit. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The application-phskck package has been identified as containing malicious code, posing significant risks to systems where it is installed. Immediate action is required to remove the package and secure any compromised information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for application-phskck →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information that may have been compromised.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

While removing the package is essential, a full system audit and restoration from backups may be necessary to ensure all malicious software is eliminated.

Yes, consider researching and using other npm packages that offer similar functionalities without the associated risks of malicious code.

How To Fix

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

npm uninstall application-phskck

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