Critical Malicious Code Vulnerability in @posthog/postgres-plugin: Token Theft and Home Directory Destruction

@posthog/postgres-plugin Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191298: Malicious code in @posthog/postgres-plugin (npm). Affects @posthog/postgres-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/postgres-plugin is an npm package designed to facilitate integration with PostgreSQL databases for analytics and data tracking. It is widely used in applications that require robust data handling and reporting capabilities. However, this package has been compromised, making it vulnerable to severe security threats that can affect users' credentials and system integrity.

Vulnerability Detail

The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. Furthermore, it can propagate itself to other npm packages owned by the user, establishing persistence through GitHub actions. The malicious payload poses a significant risk as it may also lead to the destruction of the user's home directory, resulting in data loss and system compromise.

How To Fix

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

npm uninstall @posthog/postgres-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, users are advised to remove the @posthog/postgres-plugin package from their project until a secure version is confirmed. This can be done using the command: npm uninstall @posthog/postgres-plugin. Additionally, monitor your system for any unauthorized access or changes.

Conclusion

The @posthog/postgres-plugin has been compromised by a malicious worm that poses serious security threats, including token theft and potential data loss. Immediate action is required to update or remove the affected package to protect your system and data.

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

Share this vulnerability

FAQ

The malicious code is designed to steal tokens and credentials, publish them to GitHub, and potentially destroy the user's home directory.

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 without any signup.

If you have installed the compromised version, immediately uninstall the package and update to the latest secure version.

Yes, the malicious payload may lead to the destruction of the user's home directory, resulting in potential data loss.

The worm can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions.

How To Fix

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

npm uninstall @posthog/postgres-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