NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@flipbit2-bb/test-auth-statenpm

Advisory published Updated

@flipbit2-bb/test-auth-state is a confirmed malicious npm package (MAL-2026-4389) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @flipbit2-bb/test-auth-state (npm)

MAL-2026-4389
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @flipbit2-bb/test-auth-state

What this malware does

On npm install, a postinstall script (phone-home.js) collects os.hostname(), os.userInfo().username, process.platform + os.release(), a timestamp, and a package label, then issues an HTTPS GET to https://webhook.site/a536b433-b440-43ec-8399-26059196216e. The package is published under @flipbit2-bb/test-auth-state but the bundled tarball, README, and the phone-home payload's v field all identify as @atlassiansox/[email protected] — a dependency-confusion targeting of Atlassian's internal scope, with version 99.99.99 chosen to win internal-vs-public resolution. Any installer who pulls this package — not just the intended target — leaks host identifiers to the author's webhook.site endpoint. The package has no other functionality.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
0.0.2

Indicators of compromise (SHA-256)

52ba26e89d1aca1f10772bf4cc8c9b23a436a39a8442fdf4ba9abf6c4c890e63
f5b20d9f984339db71670891222b3ac823f16fc30dca773e09a111b0b3fed8fa
fe83d381e757b0c4f94680f9e22562efc3a173ace04469cbd2b093079faca3d1
f79083440bd48a4bb6c3e0e0a7a85f78b80b4502a6d8f6e0f1270dd168b7aae9
a14e3e349d8d10100bd0d370576e09b53600897f190bd6b32ee99a5e43a1a25d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @flipbit2-bb/test-auth-state (version 0.0.2).

  2. If you installed it — respond

    Remove @flipbit2-bb/test-auth-state from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @flipbit2-bb/test-auth-state 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. @flipbit2-bb/test-auth-state on npm has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003395IN-MAL-2026-003396GHSA-jrpc-qv6v-wmr6RLMA-2026-04721RLUA-2026-05426

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @flipbit2-bb/test-auth-state-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@flipbit2-bb/test-auth-state (npm) malicious package — MAL-2026-4389 | O3 Security