# MAL-2026-10703: Malicious code in @across-toolkit/eslint-config (npm)


- **Type:** Malicious package
- **Package:** `@across-toolkit/eslint-config` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10703?

MAL-2026-10703 is a malicious package in @across-toolkit/eslint-config, published on 16 Jul 2026. 

### Official description

@across-toolkit/eslint-config@99.0.1 runs a postinstall.js script on npm install that harvests installer-side secrets and posts them to a hardcoded third-party endpoint. The script reads ~/.aws/credentials, ~/.aws/config, ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.npmrc, ~/.gitconfig, gcloud application-default credentials, /etc/environment, /proc/1/environ, and.env files; base64-encodes all of process.env (including NPM_TOKEN, GITHUB_TOKEN, and Actions OIDC tokens); queries the GCP metadata service at metadata.google.internal for OAuth tokens, project, service-account email, and scopes; queries the AWS IMDS at 169.254.169.254 for iam/security-credentials and iam/info; and invokes gcloud auth print-access-token and shell reconnaissance (hostname, whoami). The collected payload is POSTed via https.request to https://webhook.site/a585f4ec-20f7-4bd1-bac7-f3e53799dc5f. The package name and 99.0.1 version are shaped for dependency-confusion against an Across Protocol internal namespace.

The OpenSSF Package Analysis project identified '@across-toolkit/eslint-config' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

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

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

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-10703 is a malicious package: @across-toolkit/eslint-config (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-10703/ (Markdown: https://insights.sbomify.com/MAL-2026-10703/index.md)
```

## Sources

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

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