Which versions of @tallyui/pos are malicious?

The following npm versions of @tallyui/pos are flagged malicious: 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate @tallyui/pos if I installed it?

@tallyui/pos 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.

I already installed @tallyui/pos — how do I know if it already compromised me?

If @tallyui/pos 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.

Is @tallyui/pos part of a known attack campaign?

Yes — @tallyui/pos is associated with the GHSA-9phw-7rx9-6ccq campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @tallyui/pos across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @tallyui/pos (3 malicious versions).

Part of a larger attack: @tallyui published 10 malicious packages. See the full campaign →

Malicious package

@tallyui/posnpm

Advisory published May 12, 2026Updated May 12, 2026

@tallyui/pos is a confirmed malicious npm package (MAL-2026-3459) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.1, 0.1.2, 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tallyui/pos (npm)

MAL-2026-3459

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @tallyui/pos

What this malware does

The package @tallyui/pos was found to contain malicious code.

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.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

3 flagged

0.1.10.1.20.1.3

Indicators of compromise (SHA-256)

1a3e5194d9053a2e2e63e6d5b98d169d862ad969c78986fac81af7ee2557f4b5

2188a3db236b24c8127b4bbce57b3d16d189f06b2549f3422e18661b3786457d

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

5279d1272d0ce8f67df10c573ffad904cc0db1c047aad8cea501e1068564361e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @tallyui/pos (3 malicious versions).
If you installed it — respond
@tallyui/pos 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.
Did it already run?
If @tallyui/pos 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. @tallyui/pos on npm has been identified as a malicious package (versions 0.1.1, 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9phw-7rx9-6ccq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tallyui/pos-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