Malicious Code Detected in @posthog/event-sequence-timer-plugin: Security Alert

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190877: Malicious code in @posthog/event-sequence-timer-plugin (npm). Affects @posthog/event-sequence-timer-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 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 @posthog/event-sequence-timer-plugin is an npm package designed to enhance event tracking capabilities within PostHog applications. It allows developers to measure and analyze user interactions effectively. However, this package has been identified to contain malicious code, posing significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within version 0.0.8 of the @posthog/event-sequence-timer-plugin. This code can potentially compromise the integrity of applications that depend on 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/event-sequence-timer-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

If an immediate update is not feasible, consider removing the @posthog/event-sequence-timer-plugin from your project until a secure version is released. You can uninstall the package using the following command: npm uninstall @posthog/event-sequence-timer-plugin.

Conclusion

The discovery of malicious code in the @posthog/event-sequence-timer-plugin underscores the importance of vigilance when using third-party packages. By updating to a secure version and utilizing monitoring tools like Vulert, developers can protect their applications from potential threats.

See every vulnerability recorded for @posthog/event-sequence-timer-plugin →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

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

As a temporary measure, consider uninstalling the package to mitigate risks until a secure version is available.

Utilize tools like Vulert to monitor your package-lock.json file for real-time alerts on vulnerabilities.

Yes, you can use tools like npm-check-updates to automate the process of checking and updating outdated npm packages.

How To Fix

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

npm uninstall @posthog/event-sequence-timer-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