Malicious Code Detected in @posthog/web-dev-server - Security Alert

@posthog/web-dev-server Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190899: Malicious code in @posthog/web-dev-server (npm). Affects @posthog/web-dev-server versions 1.0.5. 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/web-dev-server is a package used in web development, particularly for applications built with PostHog. It provides a local development server for testing and debugging purposes. However, this package has been found to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from a malicious code injection within the @posthog/web-dev-server package, specifically in version 1.0.5. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security vulnerabilities.

How To Fix

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

npm uninstall @posthog/web-dev-server

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/web-dev-server package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall @posthog/web-dev-server.

Conclusion

The discovery of malicious code in the @posthog/web-dev-server package underscores the importance of vigilance when using third-party libraries. Users are advised to update or remove the affected package to mitigate security risks. Regular monitoring and updates can help maintain application security.

See every vulnerability recorded for @posthog/web-dev-server →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check your application without any signup.

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

Regularly check for updates in your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Yes, using tools like Vulert can automate the monitoring process, alerting you to vulnerabilities as they are discovered.

How To Fix

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

npm uninstall @posthog/web-dev-server

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