NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @posthog published 56 malicious packages. See the full campaign →
Malicious package

@posthog/bitbucket-release-trackernpm

Advisory published Updated

@posthog/bitbucket-release-tracker is a confirmed malicious npm package (MAL-2025-191289) that steals credentials and exfiltrates sensitive data (malicious version 0.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @posthog/bitbucket-release-tracker (npm)

MAL-2025-191289
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @posthog/bitbucket-release-tracker

What this malware does

The package @posthog/bitbucket-release-tracker was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
0.0.8

Indicators of compromise (SHA-256)

050810e1aaf40258b194ffe92c0f8effb99a303d30449772eb782c48aff6047c
7cd4323384e4b29aac2ac56b7eea22bbaafb8579a013ff55f7d7b26f0c972a0a

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @posthog/bitbucket-release-tracker (version 0.0.8).

  2. If you installed it — respond

    @posthog/bitbucket-release-tracker is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @posthog/bitbucket-release-tracker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @posthog/bitbucket-release-tracker on npm has been identified as a malicious package (version 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @posthog/bitbucket-release-tracker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@posthog/bitbucket-release-tracker (npm) malicious package — MAL-2025-191289 | O3 Security