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

gridster-coordsnpm

Advisory published Updated

gridster-coords is a confirmed malicious npm package (MAL-2026-15535) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gridster-coords (npm)

MAL-2026-15535
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall gridster-coords

What this malware does

package.json line 11 declares the dependency 'gridster-coords' as the bare HTTPS URL https://repo.securityctrl.com/gridster-coords instead of a registry version range. On npm install, npm fetches whatever bytes that URL serves, with no version pin and no integrity check, and executes any lifecycle scripts contained in the fetched tarball on the installer's machine. The dependency key equals the package's own name (dependency-confusion shape), the version '45.0.0' is implausibly high for a package of this name, and the host repo.securityctrl.com is unrelated to any npm registry or documented publisher. The shipped source is otherwise an inert stub, so the manifest line is the entire delivery mechanism.

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

1 flagged
45.0.0

Indicators of compromise (SHA-256)

245882b881fde3396fcb6e1e14f8b0014fc64cd1d02d27f101c8fd2a0b16c944
481123175948962f940764678e4aa53bc2930a1cf39b95710b0f3b7bd9379722

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for gridster-coords (version 45.0.0).

  2. If you installed it — respond

    Remove gridster-coords 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 gridster-coords 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. gridster-coords on npm has been identified as a malicious package (version 45.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019089GHSA-fq5c-v7fm-mv99

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gridster-coords-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

gridster-coords (npm) malicious package — MAL-2026-15535 | O3 Security