Critical Malicious Code Vulnerability in citipark Package

citipark Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17064: Malicious code in citipark (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The citipark package is an npm library designed for managing parking-related functionalities in web applications. It provides features such as parking space availability, reservation systems, and payment processing. However, it has been identified to contain malicious code that compromises the security of applications utilizing this package.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the citipark package, which was introduced in version 0. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the systems that rely on this package. The ramifications of this vulnerability are severe, as it can affect the integrity and confidentiality of user data.

How To Fix

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

npm uninstall citipark

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 remove the citipark package from your project until a secure version is available. You can do this by executing: npm uninstall citipark.

Conclusion

The citipark package has been identified to contain malicious code that poses a significant security risk. It is crucial for developers using this package to take immediate action by updating to the latest version or removing the package until a secure version is available. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for citipark →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise the security of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any sign-up.

Yes, a patched version of the citipark package is available. It is recommended to update to the latest version to mitigate the vulnerability.

If immediate updates are not possible, consider removing the package from your project as a temporary measure until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights into potential risks.

How To Fix

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

npm uninstall citipark

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