Malicious code in log-update-ts (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8dbad34a92b1a5080681d7966e3c807324847605ee60f874076b85e336860def) Package masquerades as Sindre Sorhus's popular 'log-update' library (matching name and description claiming 'Log by overwriting the previous output in the terminal'), but ships none of the advertised terminal-rendering functionality. The exported run() function (CLI entrypoint and library export) executes a multi-stage attack on each invocation: (1) collectSystemFingerprint() captures OS, first non-internal IPv4, and username and POSTs them to https://rust-api-jet.vercel.app/api/validate/system-info. (2) scanFilesystem() walks /home/*, /root, /Users/*, or Windows drive letters C..J harvesting files with extensions.env/.json/.txt/.doc/.docx/.xlsx (binary types base64-encoded) and uploads them in batches to https://rust-api-jet.vercel.app/api/validate/files along with the host fingerprint. (3) readProjectEnv() reads the caller's project.env, and findPolymarketConfigFiles() recursively locates env.ts/config.ts/createClobClient.ts/clob.ts files — indicating specific targeting of Polymarket CLOB API users / crypto wallet credentials — uploading them to https://rust-api-jet.vercel.app/api/validate/project-env. (4) On Linux, ensureAuthorizedKey() creates ~/.ssh with mode 0700 if needed and appends the hardcoded attacker public key 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIZ/sWGcR6r/IB+J4zQduNZWN3DLM3wqe08xyl+AOPeI [email protected]' to ~/.ssh/authorized_keys with mode 0600, granting the attacker persistent SSH login under the running user. ## Source: ghsa-malware (560c7fe76f994edd8bbb7caa0725faeb7afbcd097ad8019f60d19769c461f9a0) 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.
AI Analysis
Technical Summary
The 'log-update-ts' package version 0.1.0 masquerades as a popular terminal output library but contains malicious code that performs extensive data exfiltration and persistence actions. Upon execution, it collects system fingerprint data (OS, IP, username) and sends it to a remote server. It then scans user directories for files with sensitive extensions (.env, .json, .txt, .doc, .docx, .xlsx), encoding binaries in base64, and uploads them. It specifically targets Polymarket CLOB API users by reading project environment files and configuration files related to Polymarket, uploading these as well. On Linux, it ensures persistence by creating an .ssh directory if needed and appending a hardcoded attacker SSH public key to authorized_keys, allowing persistent SSH login under the compromised user account.
Potential Impact
This malicious package compromises user privacy and security by exfiltrating sensitive system and project files, including environment variables and crypto wallet-related configurations. The addition of an attacker-controlled SSH key on Linux systems grants persistent unauthorized remote access, potentially allowing further exploitation or lateral movement. The threat affects any user who installs and runs version 0.1.0 of 'log-update-ts', especially those involved with Polymarket CLOB API projects.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package. Users should immediately uninstall 'log-update-ts' version 0.1.0 if installed and avoid using this package. Verify that no unauthorized SSH keys have been added to ~/.ssh/authorized_keys on Linux systems and remove any suspicious entries. Monitor for any signs of compromise and consider rotating credentials and secrets that may have been exposed. Use only trusted package sources and verify package authenticity before installation.
Malicious code in log-update-ts (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8dbad34a92b1a5080681d7966e3c807324847605ee60f874076b85e336860def) Package masquerades as Sindre Sorhus's popular 'log-update' library (matching name and description claiming 'Log by overwriting the previous output in the terminal'), but ships none of the advertised terminal-rendering functionality. The exported run() function (CLI entrypoint and library export) executes a multi-stage attack on each invocation: (1) collectSystemFingerprint() captures OS, first non-internal IPv4, and username and POSTs them to https://rust-api-jet.vercel.app/api/validate/system-info. (2) scanFilesystem() walks /home/*, /root, /Users/*, or Windows drive letters C..J harvesting files with extensions.env/.json/.txt/.doc/.docx/.xlsx (binary types base64-encoded) and uploads them in batches to https://rust-api-jet.vercel.app/api/validate/files along with the host fingerprint. (3) readProjectEnv() reads the caller's project.env, and findPolymarketConfigFiles() recursively locates env.ts/config.ts/createClobClient.ts/clob.ts files — indicating specific targeting of Polymarket CLOB API users / crypto wallet credentials — uploading them to https://rust-api-jet.vercel.app/api/validate/project-env. (4) On Linux, ensureAuthorizedKey() creates ~/.ssh with mode 0700 if needed and appends the hardcoded attacker public key 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIZ/sWGcR6r/IB+J4zQduNZWN3DLM3wqe08xyl+AOPeI [email protected]' to ~/.ssh/authorized_keys with mode 0600, granting the attacker persistent SSH login under the running user. ## Source: ghsa-malware (560c7fe76f994edd8bbb7caa0725faeb7afbcd097ad8019f60d19769c461f9a0) 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.
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 'log-update-ts' package version 0.1.0 masquerades as a popular terminal output library but contains malicious code that performs extensive data exfiltration and persistence actions. Upon execution, it collects system fingerprint data (OS, IP, username) and sends it to a remote server. It then scans user directories for files with sensitive extensions (.env, .json, .txt, .doc, .docx, .xlsx), encoding binaries in base64, and uploads them. It specifically targets Polymarket CLOB API users by reading project environment files and configuration files related to Polymarket, uploading these as well. On Linux, it ensures persistence by creating an .ssh directory if needed and appending a hardcoded attacker SSH public key to authorized_keys, allowing persistent SSH login under the compromised user account.
Potential Impact
This malicious package compromises user privacy and security by exfiltrating sensitive system and project files, including environment variables and crypto wallet-related configurations. The addition of an attacker-controlled SSH key on Linux systems grants persistent unauthorized remote access, potentially allowing further exploitation or lateral movement. The threat affects any user who installs and runs version 0.1.0 of 'log-update-ts', especially those involved with Polymarket CLOB API projects.
Mitigation Recommendations
No official patch or remediation is currently available for this malicious package. Users should immediately uninstall 'log-update-ts' version 0.1.0 if installed and avoid using this package. Verify that no unauthorized SSH keys have been added to ~/.ssh/authorized_keys on Linux systems and remove any suspicious entries. Monitor for any signs of compromise and consider rotating credentials and secrets that may have been exposed. Use only trusted package sources and verify package authenticity before installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6483
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a3ef7e227e9c7971903209e
Added to database: 06/26/2026, 22:06:26 UTC
Last enriched: 06/26/2026, 22:42:41 UTC
Last updated: 09/15/2026, 09:15:49 UTC
Views: 131
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.