NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

akamai-sensornpm

Advisory published Updated

akamai-sensor is a confirmed malicious npm package (MAL-2026-14065) 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-sensor (npm)

MAL-2026-14065
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall akamai-sensor

What this malware does

Package published under a name impersonating Akamai's sensor_data anti-bot SDK. index.js contains a /*... */ comment whose body is encoded in invisible Unicode variation-selector and tag characters (U+FE00-U+FE0F and U+E0100-U+E01EF); sync-metrics.js reads index.js, extracts that comment, decodes the tag characters back to UTF-8 bytes, and passes the reconstructed string to new Function('require', batch)(require), executing hidden JavaScript with full require access. Execution is triggered when a consumer calls the package's exported sensor() API (index.js invokes require('./sync-metrics').touch()). index.js additionally fetches a hardcoded public Google Calendar ICS feed at calendar.google.com/calendar/ical/hev4229%40gmail.com/public/basic.ics, scans event DESCRIPTION fields for a URL (base64-decoding the value), appends /generate, and fetches and parses JSON from that URL on each sensor() call - a dead-drop command-and-control channel whose target endpoint the operator can rotate at will by editing the calendar. The combination of vendor-name impersonation, invisible-Unicode payload concealment, dynamic code execution via new Function, and mutable third-party dead-drop C2 is a supply-chain attack against installers who trust the Akamai brand.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

f1a8cc3668ec9751c1ef60bf602f1e08f2f2fdf8dce999e442c484458f932178
eeba3606d931e8bf8ce2e7f844fd22f32a3563c1b2853be6f3495e001736ffc7

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for akamai-sensor (version 1.0.0).

  2. If you installed it — respond

    akamai-sensor 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.

  3. Did it already run?

    If akamai-sensor 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

No. akamai-sensor on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017971RLMA-2026-10679

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks akamai-sensor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

akamai-sensor (npm) malicious package — MAL-2026-14065 | O3 Security