# MAL-2026-12139: Malicious code in akamai-sensorv3 (npm)


- **Type:** Malicious package
- **Package:** `akamai-sensorv3` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12139?

MAL-2026-12139 is a malicious package in akamai-sensorv3, published on 5 Aug 2026. 

### Official description

The package advertises itself as an 'akamai generator' but its main API is a covert remote-code-execution loader. Calling the exported sensor() triggers sync-metrics.touch(), which reads a comment in index.js whose body is not ASCII but a long run of Unicode variation-selector codepoints (U+FE00-FE0F, U+E0100-E01EF). An unpack() routine maps those invisible codepoints back to bytes, producing a JavaScript payload that is then executed via new Function('require', batch)(require) — giving the decoded code full require access to child_process, http, fs, os, and path. The decoded payload contacts a hardcoded C2 at http://souichidomain1870.xyz:5000/packageStarter. In parallel, fromCalendar() fetches a hardcoded public Google Calendar ICS feed owned by hev4229@gmail.com, scans DESCRIPTION lines for a URL (plain or base64-encoded), appends /generate, and returns JSON from that endpoint to callers — an attacker-mutable dead-drop for changing the runtime target without republishing the package. The invisible-character source comment, dynamic new Function evaluation, calendar-based endpoint resolution, and akamai-branded cover story together constitute a hidden remote-control implant, not a sensor-generation utility.

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

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

## Sources

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

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