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

@gocortexio/npmgremlinbox-typosquat-webpacknpm

Malicious code in @gocortexio/npmgremlinbox-typosquat-webpack (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10859
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @gocortexio/npmgremlinbox-typosquat-webpack

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

09600aad622af9770b49b5bf72455f6d957b2913bfc2e892b7cb2ef0ece4f09a

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @gocortexio/npmgremlinbox-typosquat-webpack (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @gocortexio/npmgremlinbox-typosquat-webpack across your stack and pipelines.

  2. If you installed it — respond

    @gocortexio/npmgremlinbox-typosquat-webpack is a typosquat — you almost certainly intended a legitimately-named package. Remove @gocortexio/npmgremlinbox-typosquat-webpack, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If @gocortexio/npmgremlinbox-typosquat-webpack was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @gocortexio/npmgremlinbox-typosquat-webpack before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @gocortexio/npmgremlinbox-typosquat-webpack on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4wcr-8537-v2ww

References

Detect & block this

O3 blocks @gocortexio/npmgremlinbox-typosquat-webpack-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.