# MAL-2026-14066: Malicious code in akamaijs-sensorv1 (npm)


- **Type:** Malicious package
- **Package:** `akamaijs-sensorv1` (npm)
- **Published:** 15 Aug 2026
- **Also known as:** GHSA-vf6f-mfc3-9548

## What is MAL-2026-14066?

MAL-2026-14066 is a malicious package in akamaijs-sensorv1, published on 15 Aug 2026. 

### Official description

The package advertises itself as an Akamai Bot Manager sensor generator, but its main entry conceals its real behavior. index.js contains a comment composed of invisible Unicode tag / variation-selector code points (U+FE00-U+FE0F and U+E0100-U+E01EF). sync-metrics.js reads the package's own index.js, decodes those invisible characters back into bytes, and executes the resulting string via new Function('require', batch)(require) — a hidden dynamic-eval sink that runs whenever a consumer invokes the exported sensor() API. sensor() additionally fetches a hardcoded public Google Calendar ICS feed (calendar.google.com/calendar/ical/hev4229%40gmail.com/public/basic.ics), parses the newest event's DESCRIPTION field for a URL (accepting plain text, href, or base64-encoded forms), rewrites it to end in /generate, issues a GET to that URL, and returns the response as JSON to the caller. The network destination the installer's process contacts is therefore controlled by whoever owns the hev4229@gmail.com calendar and can be changed at any time by editing a calendar event, with no pinning, signing, or authentication of the retrieved URL. The invisible-character steganography, hidden eval, calendar-based dead-drop C2, and Akamai-lure package name together form a covert remote-code / attacker-controlled-redirector channel.

## What should I do about MAL-2026-14066?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14066 is a malicious package: akamaijs-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-14066/ (Markdown: https://insights.sbomify.com/MAL-2026-14066/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14066

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14066/
Summaries are generated and may contain mistakes; the official description above is the record.