Critical Malicious Code Vulnerability in @posthog/icons Package

@posthog/icons Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191292: Malicious code in @posthog/icons (npm). Affects @posthog/icons versions 0.36.1. 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/icons package is a popular npm library used for providing a set of icons for PostHog applications. It is widely utilized in web development to enhance user interfaces with visually appealing icons. However, this package has recently been compromised, making it vulnerable to severe security threats.

Vulnerability Detail

The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @posthog/icons package. This malicious code is designed to steal sensitive tokens and credentials from users, subsequently publishing them to GitHub. The worm can propagate itself to other npm packages owned by the user and establish persistence through a GitHub action. Additionally, it poses a risk of destroying the user's home directory, leading to significant data loss.

How To Fix

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

npm uninstall @posthog/icons

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 can remove the @posthog/icons package from their project until a secure version is released. This can be done using the command: npm uninstall @posthog/icons. Additionally, consider using alternative icon libraries that are not affected by this vulnerability.

Conclusion

The @posthog/icons package has been compromised by a malicious worm that poses significant security risks to users. It is essential to take immediate action by updating or removing the package to safeguard your applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain security.

See every vulnerability recorded for @posthog/icons →

Share this vulnerability

FAQ

The vulnerability involves malicious code that steals user tokens and credentials, potentially leading to unauthorized access to sensitive information.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner without any signup.

If you have installed the compromised version, it is crucial to uninstall the package immediately and update to a secure version as soon as it is available.

Yes, the worm can propagate itself to other npm packages owned by the user, increasing the risk of widespread compromise.

The potential consequences include unauthorized access to sensitive data, loss of user credentials, and possible destruction of the user's home directory.

How To Fix

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

npm uninstall @posthog/icons

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