# MAL-2026-4263: Malicious code in secdriven (npm)


- **Type:** Malicious package
- **Package:** `secdriven` (npm)
- **Published:** 23 May 2026

## What is MAL-2026-4263?

MAL-2026-4263 is a malicious package in secdriven, published on 23 May 2026. 

### Official description

On `npm install`, postinstall.js executes `whoami` via child_process and reads os.hostname(), os.platform(), the working directory, and CI / GITHUB_REPOSITORY environment variables, then transmits them as query-string parameters in an HTTPS GET to a hardcoded interactsh subdomain (`lg5ys3jebfzwk366pilidbmah1nsbszh.oastify.com`) under the path `/google/secdriven/`. A DNS lookup using `whoami` output as a subdomain provides a fallback exfiltration channel. The package description ("Security research canary — Google") and README pointing at a Google CTF internal package.json indicate this is a dependency-confusion payload targeting Google's internal namespace; any installer whose resolver picks up this public name leaks host identity, username, working directory, and CI repository path to the third-party OOB-detection endpoint without consent. Whether published as research or attack, the installer-side effect is the same: unconsented identity-and-environment beacon at install time.

The OpenSSF Package Analysis project identified 'secdriven' @ 1.0.8 (npm) as malicious.

It is considered malicious because:

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

- The package executes one or more commands associated with malicious behavior.

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

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

## Sources

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

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