trapp-check-logsnpm
trapp-check-logs is a confirmed malicious npm package (MAL-2026-12286) that typosquats a legitimate package to trick installs (malicious version 20.1.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in trapp-check-logs (npm)
What this malware does
On require of the package, index.js loads bridge.js which selects a platform-specific payload path, fetches bytes over HTTPS from string-concatenation-obfuscated hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) assembled at runtime via array-join fragments, writes them to /tmp or %TEMP% under disguised names such as.cache<rand> and dotnet_diag_<rand>.exe, chmods 0755, and spawns them detached via /bin/sh -c or cmd.exe /c start /b. If the HTTPS mirrors fail, _bridge.js falls back to a DNS TXT-record channel against tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site, querying c.<domain> for a chunk count and then <i>.<domain> for base64 fragments that are concatenated, decoded, written to disk and executed as a native binary. The package's README advertises only a trivial in-process logger; the hostname obfuscation, per-OS payload selection, hidden temp staging with system-tool-mimicking names, detached spawning, and DNS-tunneled code delivery are exclusively attack behaviors and produce full-host code execution on any consumer that installs or requires this package.
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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for trapp-check-logs (version 20.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging trapp-check-logs across your stack and pipelines.
If you installed it — respond
trapp-check-logs is a typosquat — you almost certainly intended a legitimately-named package. Remove trapp-check-logs, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If trapp-check-logs 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 trapp-check-logs 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 trapp-check-logs-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.