Malicious Code Detected in Personalizationtrkserv Package - Vulnerability MAL-2025-6947

personalizationtrkserv Updated 02 Oct 2025

Summary

17/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6947: Malicious code in personalizationtrkserv (npm). Affects personalizationtrkserv versions >= 10.0.0. 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 'personalizationtrkserv' package is an npm module designed for personalization tracking services. It is used by developers to integrate tracking functionalities into their applications. However, this package has been flagged for malicious activity, specifically for communicating with domains associated with harmful behavior, which poses a significant risk to applications utilizing it.

Vulnerability Detail

The vulnerability arises from the package's ability to execute commands linked to malicious behavior. This issue was identified by the OpenSSF Package Analysis project, which flagged versions 11.0.0 and 11.0.1 of 'personalizationtrkserv' as malicious due to their communication with a domain known for malicious activities. The ramifications of this vulnerability include potential data breaches, unauthorized access to sensitive information, and the risk of the application being compromised.

How To Fix

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

npm uninstall personalizationtrkserv

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

If immediate updating is not feasible, consider removing the package from your project until a secure version is released. You can uninstall the package using the following command:

npm uninstall personalizationtrkserv --save

Conclusion

The 'personalizationtrkserv' package has been identified as malicious due to its association with harmful activities. It is crucial for developers to update or remove this package to safeguard their applications from potential threats. Regular monitoring of dependencies is essential to maintain application security.

See every vulnerability recorded for personalizationtrkserv →

Share this vulnerability

FAQ

It is an npm module used for integrating personalization tracking services into applications.

The package has been found to communicate with domains associated with malicious activities and execute harmful commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Consider removing the package from your project until a secure version is available.

Utilize tools like Vulert to monitor your package-lock.json for vulnerabilities without requiring code access or installation.

How To Fix

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

npm uninstall personalizationtrkserv

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