Malicious Code Detected in @posthog/pagerduty-plugin: Security Alert

@posthog/pagerduty-plugin Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190888: Malicious code in @posthog/pagerduty-plugin (npm). Affects @posthog/pagerduty-plugin versions 0.0.8. 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 @posthog/pagerduty-plugin is an npm package designed to integrate PostHog with PagerDuty, enabling users to manage alerts and incidents effectively. This package is utilized in various applications to enhance monitoring and incident response capabilities. However, it has recently been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability originates from a malicious code injection found in version 0.0.8 of the @posthog/pagerduty-plugin package. This code can potentially compromise the integrity of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The malicious code was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall @posthog/pagerduty-plugin

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 @posthog/pagerduty-plugin package from your project until a secure version is released. You can do this by running the following command: npm uninstall @posthog/pagerduty-plugin.

Conclusion

The @posthog/pagerduty-plugin package has been identified to contain malicious code, posing a significant risk to applications that utilize it. Users are advised to update or remove the package to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help in identifying such vulnerabilities in real-time.

See every vulnerability recorded for @posthog/pagerduty-plugin →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that utilize this package.

You can use the Vulert platform 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.

Currently, there is no specific patched version mentioned in the details. It is advisable to monitor the package repository for updates.

If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks.

The vulnerability was discovered by Amazon Inspector, a security assessment service that identifies vulnerabilities in software packages.

How To Fix

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

npm uninstall @posthog/pagerduty-plugin

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