Which versions of ty-web-session are malicious?

The following npm versions of ty-web-session are flagged malicious: 3.0.1. Treat any of these as compromised.

How do I remediate ty-web-session if I installed it?

Remove ty-web-session 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 ty-web-session — how do I know if it already compromised me?

If ty-web-session 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.

How do I find ty-web-session across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ty-web-session (version 3.0.1).

Malicious package

ty-web-sessionnpm

Advisory published Mar 20, 2026Updated Mar 23, 2026

ty-web-session is a confirmed malicious npm package (MAL-2026-1997) that executes malicious code on install (malicious version 3.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ty-web-session (npm)

MAL-2026-1997

Immediate action

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

npm uninstall ty-web-session

What this malware does

The package ty-web-session was found to contain malicious code.

The OpenSSF Package Analysis project identified 'ty-web-session' @ 3.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

3.0.1

Indicators of compromise (SHA-256)

9507cb60c86468a7c12b26e35e0501ebd750e48a8e7decbc5996460e1c229e95

15f6d0a640d7d4323f1ef52969a6a259b9b6e3bacc2bf65f514cd618a00945a9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ty-web-session (version 3.0.1).
If you installed it — respond
Remove ty-web-session 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 ty-web-session 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. ty-web-session on npm has been identified as a malicious package (version 3.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks ty-web-session-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