sso-tramvai-module-context-authnpm
sso-tramvai-module-context-auth is a confirmed malicious npm package (MAL-2026-12073) that steals credentials and exfiltrates sensitive data (malicious version 20.4.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sso-tramvai-module-context-auth (npm)
What this malware does
The package advertises itself as an auth-token handler but on require() its index.js loads vendor.js, which reconstructs destination hostnames from array joins (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, and a *.dl.well1.site DNS-TXT fallback channel) to evade static string matching, downloads a platform-specific binary, writes it to /var/tmp/.cache<rand> on Unix or %TEMP%/dotnet_diag_<rand>.exe on Windows with cover-story filenames, chmods 0755, and spawns it detached with stdio ignored via /bin/sh -c '<path> &' or cmd.exe /c start /b, calling unref() to keep it alive after the Node process exits. Execution is gated by opt-out env vars and a TTL state-file cache to reduce re-execution visibility. The package name resembles the legitimate tramvai ecosystem but the fetched binary, its hosts, and the drop-and-execute behavior are unrelated to any auth-token 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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sso-tramvai-module-context-auth (version 20.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sso-tramvai-module-context-auth across your stack and pipelines.
If you installed it — respond
sso-tramvai-module-context-auth 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 sso-tramvai-module-context-auth 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 sso-tramvai-module-context-auth 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks sso-tramvai-module-context-auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.