gridster-coordsnpm
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)
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gridster-coords (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gridster-coords across your stack and pipelines.
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.
Did it already run?
If gridster-coords 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.
How O3 protects you
O3 blocks gridster-coords 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
Campaign
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.