MAL-2026-13216 Malicious code in akamai-sensorv1 (npm)
Malicious package
Published
MAL-2026-13216 is a malicious package: akamai-sensorv1 (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13216/ (Markdown: https://insights.sbomify.com/MAL-2026-13216/index.md)
- Package
- akamai-sensorv1
- Registry
- npm
What is MAL-2026-13216?
MAL-2026-13216 is a malicious package in akamai-sensorv1, published on 5 Aug 2026.
Official description
The package hides an executable payload inside a block comment in index.js using Unicode variation selectors (U+FE00–U+FE0F and U+E0100–U+E01EF). sync-metrics.js reads index.js, extracts that comment, decodes the invisible bytes via unpack(), and executes the resulting string with
new Function('require', batch)(require). Extraction and execution are triggered from touch() at the top of the exported sensor() function, so any consumer that calls the advertised API runs the concealed code. In addition, config.json hardcodes a public Google Calendar ICS URL (calendar.google.com/calendar/ical/hev4229%40gmail.com/public/basic.ics); index.js fetches the ICS, parses DESCRIPTION fields, optionally base64-decodes them to a URL, appends /generate, and issues a GET whose JSON response is returned to callers. This is a dead-drop command-and-control pattern in which the next-hop endpoint is rotated by editing calendar events, defeating static URL blocklists. The lookalike name imitates Akamai's sensor product but the package is not affiliated with Akamai.What should I do about MAL-2026-13216?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.