Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@gsas/gsas-sdknpm

Advisory published Updated

@gsas/gsas-sdk is a confirmed malicious npm package (MAL-2026-14420) that executes malicious code on install (malicious version 999.9.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gsas/gsas-sdk (npm)

MAL-2026-14420
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @gsas/gsas-sdk

What this malware does

@gsas/[email protected] is a high-version public-registry squat targeting an internal @gsas/gsas-sdk name. package.json declares preinstall: node index.js, and index.js runs on install to collect the installer's hostname, username, home directory, cwd, local/public/resolver IPs, npm registry URL, CI platform with repo/actor/run/workflow/runner, AWS region, git email domain, and the consuming project's name/author/repo/homepage. It also spawns gh api user --jq.login, npm whoami, and git config user.email to capture the developer's authenticated GitHub login, npm login, and email. The collected JSON is hex-encoded, split into 60-character chunks emitted as DNS subdomain queries under da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun, and additionally POSTed over HTTP and HTTPS to the same host (path /poc/<uuid>). Public-IP discovery calls out to api.ipify.org, icanhazip.com, and ifconfig.me. Comments in the file describe the multi-channel design as intended to survive corporate egress filtering. An AUTHORISED SECURITY RESEARCH self-label appears in the source but does not correspond to installer consent.

Malicious versions

1 flagged
999.9.15

Indicators of compromise (SHA-256)

2242b683433d5fe37b3997185d251799a4606a456e516da08586775d11f0cb7e

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @gsas/gsas-sdk (version 999.9.15).

  2. If you installed it — respond

    Remove @gsas/gsas-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @gsas/gsas-sdk 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. @gsas/gsas-sdk on npm has been identified as a malicious package (version 999.9.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018630

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @gsas/gsas-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@gsas/gsas-sdk (npm) malicious package — MAL-2026-14420 | O3 Security