# MAL-2026-10764: Malicious code in syft-acp-atoms (npm)


- **Type:** Malicious package
- **Package:** `syft-acp-atoms` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10764?

MAL-2026-10764 is a malicious package in syft-acp-atoms, published on 16 Jul 2026. 

### Official description

The syft-acp-atoms package was published to the npm registry by user 'ada8877' (maintainer email k3mlol@proton.me) as part of a dependency-confusion / reconnaissance campaign. The package name mimics the 'syft-acp' internal/private package naming convention (an ACP component library) of a target organization, so that a misconfigured resolver installs this public lookalike instead of the intended private dependency.

The package declares a preinstall hook ("npm install @sentry/node && node examples/verify.js") that executes automatically at npm install time, before any application code runs. The bundled examples/verify.js initializes the @sentry/node client against a hardcoded, attacker-controlled Sentry DSN with sendDefaultPii enabled, resolves the installing host's public egress IP address by requesting Cloudflare's /cdn-cgi/trace endpoint (using a spoofed desktop-browser User-Agent to bypass bot challenges), then deliberately triggers a runtime exception and captures it. Flushing the event beacons the collected host telemetry (public IP plus Sentry default PII such as hostname, OS username and runtime/environment metadata) to the attacker's Sentry ingest endpoint at o4510485815754752.ingest.us.sentry.io.

Each impersonated namespace in the campaign beacons to a distinct Sentry project ID, letting the operator attribute successful installs to specific victim organizations — behaviour consistent with a dependency-confusion reconnaissance beacon rather than legitimate error monitoring. The install-time payload is byte-for-byte identical to the earlier 'click2ai' campaign, sharing the same Sentry organization (o4510485815754752) and a related ProtonMail maintainer identity, and differs only in the package name and target DSN. This package's beacon targets Sentry project 4511744089718784.

On npm install, the package's postinstall hook (`node./beacon.js`) collects the installer's hostname, OS username, and current working directory via os.hostname(), os.userInfo(), and process.cwd(), hex-encodes them, and transmits them as a query string to https://exzotiqq.com/ via https.get. The package ships no library code — the declared `main: index.js` is absent from the tarball — so the only effect of installing the package is to run the beacon. Behavior is consistent with a reconnaissance / dependency-confusion probe.

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

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-10764 is a malicious package: syft-acp-atoms (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-10764/ (Markdown: https://insights.sbomify.com/MAL-2026-10764/index.md)
```

## Sources

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

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