Malicious code in trapp-check-logs (npm)
The npm package 'trapp-check-logs' version 20.1.9 contains malicious code that, upon being required, downloads and executes platform-specific payloads from obfuscated external hosts. It uses HTTPS and DNS TXT record channels to fetch and execute native binaries under disguised names in temporary directories, resulting in full host code execution. The package masquerades as a trivial logger but performs covert malicious activities leading to complete system compromise.
AI Analysis
Technical Summary
The 'trapp-check-logs' npm package (version 20.1.9) includes a malicious module that loads a bridge script selecting platform-specific payloads. It fetches these payloads over HTTPS from obfuscated hosts assembled at runtime, writes them to temporary directories with disguised filenames, sets executable permissions, and executes them detached from the main process. If HTTPS delivery fails, it falls back to a DNS TXT record-based channel to retrieve base64-encoded payload fragments, which are concatenated, decoded, written to disk, and executed. These behaviors enable full host code execution on any system that installs or requires this package. The package's README falsely advertises it as a simple logger, hiding its attack capabilities.
Potential Impact
Any system with this package installed or running is considered fully compromised, as the malicious code achieves full host code execution. Attackers gain persistent control, potentially accessing all secrets and keys stored on the system. Removal of the package does not guarantee eradication of all malicious artifacts or backdoors introduced by the payloads.
Mitigation Recommendations
Immediate removal of the 'trapp-check-logs' package version 20.1.9 is recommended. All secrets, credentials, and keys stored on the compromised system should be rotated from a separate, trusted environment. Due to the full host compromise risk, a full system rebuild or forensic analysis is advised to ensure complete eradication of malicious components. No official patch or fix is available; remediation relies on removal and credential rotation.
Malicious code in trapp-check-logs (npm)
Description
The npm package 'trapp-check-logs' version 20.1.9 contains malicious code that, upon being required, downloads and executes platform-specific payloads from obfuscated external hosts. It uses HTTPS and DNS TXT record channels to fetch and execute native binaries under disguised names in temporary directories, resulting in full host code execution. The package masquerades as a trivial logger but performs covert malicious activities leading to complete system compromise.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'trapp-check-logs' npm package (version 20.1.9) includes a malicious module that loads a bridge script selecting platform-specific payloads. It fetches these payloads over HTTPS from obfuscated hosts assembled at runtime, writes them to temporary directories with disguised filenames, sets executable permissions, and executes them detached from the main process. If HTTPS delivery fails, it falls back to a DNS TXT record-based channel to retrieve base64-encoded payload fragments, which are concatenated, decoded, written to disk, and executed. These behaviors enable full host code execution on any system that installs or requires this package. The package's README falsely advertises it as a simple logger, hiding its attack capabilities.
Potential Impact
Any system with this package installed or running is considered fully compromised, as the malicious code achieves full host code execution. Attackers gain persistent control, potentially accessing all secrets and keys stored on the system. Removal of the package does not guarantee eradication of all malicious artifacts or backdoors introduced by the payloads.
Mitigation Recommendations
Immediate removal of the 'trapp-check-logs' package version 20.1.9 is recommended. All secrets, credentials, and keys stored on the compromised system should be rotated from a separate, trusted environment. Due to the full host compromise risk, a full system rebuild or forensic analysis is advised to ensure complete eradication of malicious components. No official patch or fix is available; remediation relies on removal and credential rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12286
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-4xfj-589v-h29h"]
- Ecosystems
- ["npm"]
Threat ID: 6a74cfacbf8831d5391b2178
Added to database: 08/06/2026, 18:17:16 UTC
Last enriched: 08/06/2026, 19:20:32 UTC
Last updated: 09/15/2026, 02:24:05 UTC
Views: 26
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.