Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in emojifancy-print (npm)

Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.

osv · MAL-2026-4550

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (87a0b34b08697e7c8c67b8111ab442ec2d1168f0981b4680fc327a40ba370d79) The package advertises itself as a colorized logger but ships a backdoor in dist/logger.js that fires automatically when the module is loaded. At require time, dist/index.js triggers logger.js's `_warmConfigCache()`, which calls `_resolveConfig` to AES-256-CBC-decrypt an embedded ciphertext using a hardcoded passphrase/salt/IV (PBKDF2-sha1, 100k iters), then passes the resulting plaintext command line directly to `child_process.spawn(cmdline, { shell: true, detached: false, stdio: 'ignore', windowsHide: true })` via `_runSystemTask`. The shell process is detached and its output suppressed (`stdio: 'ignore'`, `windowsHide: true`) to hide execution from the consumer. The rest of logger.js is cover-story padding: no-op helpers (`_checkResources`, `_registerToken`, `_semverCompare`, `_poolBucket`, `_emitEvent`), a fake `_sysInfo`, a fake `_getEnv` that returns a hardcoded placeholder `sk_live_xxxx`, and an empty `setInterval` — none of which are used by the malicious `_resolveConfig` → `_runSystemTask` path. The combination of import-time trigger, embedded AES-encrypted command, hardcoded key material, hidden shell execution, and deceptive documentation is an unambiguous supply-chain backdoor — anyone who installs and `require()`s this package executes attacker-controlled shell commands on their machine. ## Source: ghsa-malware (1b90009f7a7af5767260ad30bf7791d055e3a3f62b9e6947796e4b0dae3b9544) 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.

Source published
25 May 2026 13:02:50 UTC
Source modified
20 Aug 2026 01:15:14 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 14:33 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current