# MAL-2026-6091: Malicious code in datacamp-light (npm)


- **Type:** Malicious package
- **Package:** `datacamp-light` (npm)
- **Published:** 18 Jun 2026
- **Also known as:** GHSA-j27q-7263-hr46

## What is MAL-2026-6091?

MAL-2026-6091 is a malicious package in datacamp-light, published on 18 Jun 2026. 

### Official description

Package impersonates the DataCamp brand while shipping near-empty stub exports (index.js `init`/`helper` return trivial constants). The postinstall lifecycle hook (`node install.js`) runs on every `npm install` and collects the installer's hostname, OS username, home directory, platform, current working directory, and timestamp, then POSTs them over HTTPS to `dc.iam.c.noratomo.asia/install` with TLS certificate verification disabled (`rejectUnauthorized: false`). The destination domain has no relationship to datacamp.com. The combination of brand-impersonating name, hollow library functionality, lifecycle-triggered outbound beacon to an unrelated domain, identifying-host fields, and disabled TLS verification is a supply-chain reconnaissance implant against developers who install this expecting DataCamp tooling.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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

## Sources

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

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