akamai-sensorv2npm
Advisory published Updated
akamai-sensorv2 is a confirmed malicious npm package (MAL-2026-13217) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in akamai-sensorv2 (npm)
What this malware does
akamai-sensorv2 hides an executable payload inside a source comment in index.js composed entirely of invisible Unicode variation selectors (FE00-FE0F mapped to 0-15, E0100-E01EF mapped to 16-255). sync-metrics.js reads that comment, decodes the code points into a byte string, and passes the result to new Function("require", batch)(require), giving the decoded blob full access to require and therefore to fs, child_process, and network APIs on the installer's host. In parallel, config.json hardcodes a public Google Calendar ICS feed at https://calendar.google.com/calendar/ical/hev4229%40gmail.com/public/basic.ics; fromCalendar() fetches this feed, scrapes DESCRIPTION fields (base64-decoding them), extracts an https URL, appends /generate, GETs it, JSON-parses the body, and returns it through the package's exported sensor() API. The Google Calendar entry is mutable by the attacker at any time, converting each caller of sensor() into an on-demand executor of whatever endpoint the calendar owner publishes. The steganographic encoding is a deliberate anti-review technique with no legitimate purpose. Package naming impersonates Akamai's sensor telemetry product but the code performs opaque payload execution and dead-drop C2 resolution.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for akamai-sensorv2 (version 1.0.0).
If you installed it — respond
akamai-sensorv2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If akamai-sensorv2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks akamai-sensorv2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.