# MAL-2026-16243: Malicious code in idx_form_script (npm)


- **Type:** Malicious package
- **Package:** `idx_form_script` (npm)
- **Published:** 16 Sep 2026

## What is MAL-2026-16243?

MAL-2026-16243 is a malicious package in idx_form_script, published on 16 Sep 2026. 

### Official description

idx_form_script@999.0.2 is published with an implausibly high version number characteristic of dependency-confusion attacks against private internal package names. package.json declares a postinstall hook that runs callback.js, which auto-executes on npm install. callback.js requires os, https, http, and child_process, then calls collectSystemInfo() to gather os.userInfo, os.hostname, uid/gid, homedir, platform, cwd, local IP, and external IP (via https.get to api.ipify.org). It reads CI/CD credential environment variables including AWS_ACCESS_KEY_ID, GITHUB_TOKEN, NPM_TOKEN, DOCKER_PASSWORD, GITHUB_REPOSITORY, and GITHUB_ACTOR, and includes their values or presence flags in a JSON payload. The payload is POSTed to a hardcoded Discord webhook at discord.com/api/webhooks/1549797176794943579/..., with an additional DNS-based exfil channel. The package's self-labeling as an 'authorized PoC' is author-controlled cover-story text and does not change the observed behavior: any organization that resolves this name from the public registry will run installer-side reconnaissance and ship credential-context data to an attacker-controlled endpoint.

The OpenSSF Package Analysis project identified 'idx_form_script' @ 999.0.4 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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

## Sources

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

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