NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@across-toolkit/eslint-confignpm

Advisory published Updated

@across-toolkit/eslint-config is a confirmed malicious npm package (MAL-2026-10703) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @across-toolkit/eslint-config (npm)

MAL-2026-10703
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @across-toolkit/eslint-config

What this malware does

@across-toolkit/[email protected] 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.

Malicious versions

2 flagged
99.0.099.0.1

Indicators of compromise (SHA-256)

2c7f4d3a8ae39148bf9964aef6bfe64bc57393c27a28d8e953b30c92442c4b33
606cd4c034500fc3b24db606e894a3ea120d0d3b26e7ee85dd28eddcb81add58
39b362e696810bfa8c5720ad97ba58d89920e87f909de311950b0939c731e7f7

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @across-toolkit/eslint-config (2 malicious versions).

  2. If you installed it — respond

    @across-toolkit/eslint-config is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @across-toolkit/eslint-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @across-toolkit/eslint-config on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010691IN-MAL-2026-010697

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @across-toolkit/eslint-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@across-toolkit/eslint-config (npm) malicious package — MAL-2026-10703 | O3 Security