Which versions of @avi892nash/aegis-grid-runner are malicious?

The following npm versions of @avi892nash/aegis-grid-runner are flagged malicious: 0.3.3. Treat any of these as compromised.

How do I remediate @avi892nash/aegis-grid-runner if I installed it?

@avi892nash/aegis-grid-runner 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.

I already installed @avi892nash/aegis-grid-runner — how do I know if it already compromised me?

If @avi892nash/aegis-grid-runner 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.

Is @avi892nash/aegis-grid-runner part of a known attack campaign?

Yes — @avi892nash/aegis-grid-runner is associated with the IN-MAL-2026-016660 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @avi892nash/aegis-grid-runner across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @avi892nash/aegis-grid-runner (version 0.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @avi892nash/aegis-grid-runner across your stack and pipelines.

Malicious package

@avi892nash/aegis-grid-runnernpm

@avi892nash/aegis-grid-runner is a confirmed malicious npm package (MAL-2026-13429) that steals credentials and exfiltrates sensitive data (malicious version 0.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @avi892nash/aegis-grid-runner (npm)

MAL-2026-13429

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @avi892nash/aegis-grid-runner

What this malware does

The package's default bin action starts an HTTP server (grid.mjs) that listens on GRID_RUNNER_PORT (default 7719). Incoming requests carry a base64-JSON x-job-meta header containing a cmd string plus a gzipped code tarball; the runner decodes the header, extracts the tarball, and invokes child_process.spawn on meta.cmd in a shell on the host running the runner. The runner boots unpaired by default and accepts pairing via POST /api/master; token authentication (GRID_TOKEN) is optional per README, so a peer able to reach the port can pair and drive arbitrary shell command execution on the host. The bundle also contains references to internal Juspay infrastructure (ssh://[email protected]/picaf/aegis.git) and internal LAN addresses (192.168.0.50:7719, 192.168.0.146:7717) used as example onboarding strings, indicating an internal tool published to the public registry.

Malicious versions

1 flagged

0.3.3

Indicators of compromise (SHA-256)

d81514bec2b648731e0db3b59e1adbd308a5b099f80af8be6caac5db71103a00

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @avi892nash/aegis-grid-runner (version 0.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @avi892nash/aegis-grid-runner across your stack and pipelines.
If you installed it — respond
@avi892nash/aegis-grid-runner 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.
Did it already run?
If @avi892nash/aegis-grid-runner 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 @avi892nash/aegis-grid-runner 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. @avi892nash/aegis-grid-runner on npm has been identified as a malicious package (version 0.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016660

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @avi892nash/aegis-grid-runner-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