Malicious Code Detected in @posthog/nextjs-config Package
Summary
MAL-2025-190887: Malicious code in @posthog/nextjs-config (npm). Affects @posthog/nextjs-config versions 1.5.1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @posthog/nextjs-config package is a configuration tool for Next.js applications, designed to simplify the integration of PostHog analytics into web projects. It provides developers with essential features to track user interactions and analyze application performance. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @posthog/nextjs-config package, specifically in version 1.5.1. This malicious code can potentially compromise the security of applications that depend on this 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/nextjs-configIf 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 may consider removing the @posthog/nextjs-config package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @posthog/nextjs-config. This will help mitigate the risk associated with the malicious code.
Conclusion
The discovery of malicious code in the @posthog/nextjs-config package underscores the importance of vigilance when using third-party libraries. Developers are advised to update their dependencies regularly and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications against potential threats.
See every vulnerability recorded for @posthog/nextjs-config →
FAQ
The malicious code is designed to compromise the security of applications that use the package, potentially leading to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can identify if your application is affected by this vulnerability.
Yes, Vulert provides real-time monitoring for open-source vulnerabilities without requiring access to your code or installation. You can use the Vulert playground to check for vulnerabilities.
If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks until a secure version is available.
Detailed information about this vulnerability can be found in the vulnerability report published by Amazon Inspector, which outlines the specifics of the malicious code detected.
