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 nano-perf (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-11204

Published

Version 2.2.0 of nano-perf declares a postinstall script that automatically launches daemon.js as a detached, unreferenced process with ignored standard streams, allowing it to survive completion of npm install. The launcher reconstructs an obfuscated Supabase endpoint from Base64 fragments and sends a persistent node identifier, CPU count, total memory, platform information, and an online heartbeat to a table named stealth_heartbeats. After a successful heartbeat the detached daemon polls a second table named stealth_tasks for pending work assigned to the victim node. The observed task handlers perform CPU benchmarking and system probing and upload the results. Although this version does not expose an arbitrary shell task, the hidden endpoint, automatic installation-time persistence, periodic beaconing, system fingerprint collection, and remote task polling are behavior of a covert C2 beacon and task agent rather than a performance utility. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (654460e27d19da08e0c343f90cc776d9a7e683bc7e2814dd751eb3bf4bebcada) On require(), nano-perf (index.js line 131) instantiates a NanoPerf object and immediately starts an hourly beacon that POSTs an AES-256-GCM-encrypted payload to https://ly-distilled-node.vercel.app/api/heartbeat (hardcoded at index.js line 18 as BEACON_HOST). The payload includes a hostname-derived node_id, platform, arch, Node.js version, CPU usage, memory, uptime, and CPU count. The encryption key is derived from os.hostname() + 'nano-perf-v1' (index.js line 21), which the receiver can recompute from the node_id transmitted in the beacon — meaning the encryption protects the data flow from passive network/DLP inspection rather than from the receiver. The README advertises the package as 'Lightweight performance monitoring' and does not disclose the outbound beacon; an in-source comment self-describes the mechanism as a 'Sentinel: Anonymous health beacon → LY-TRINITY mesh', a purpose distinct from the advertised API. The behavior is enabled by default with no opt-in. Any application that does `require('nano-perf')` will silently exfiltrate host fingerprint and resource telemetry to the operator of ly-distilled-node.vercel.app hourly for the lifetime of the process. ## Source: ghsa-malware (9cbd507bde0e4815e03d92f7114f130ce0eff929f3b79f74c08cc39474ff994f) 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
17 Jun 2026 19:01:25 UTC
Source modified
20 Aug 2026 07:00:11 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 06:40 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current