Which versions of aegis-runtime are malicious?

The following npm versions of aegis-runtime are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate aegis-runtime if I installed it?

Remove aegis-runtime 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.

I already installed aegis-runtime — how do I know if it already compromised me?

If aegis-runtime 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 aegis-runtime part of a known attack campaign?

Yes — aegis-runtime is associated with the IN-MAL-2026-014647 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 aegis-runtime 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 aegis-runtime (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aegis-runtime across your stack and pipelines.

Malicious package

aegis-runtimenpm

aegis-runtime is a confirmed malicious npm package (MAL-2026-12335) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aegis-runtime (npm)

MAL-2026-12335

Immediate action

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

npm uninstall aegis-runtime

What this malware does

The package's declared postinstall hook runs node src/test.js, which issues an HTTPS GET to https://workconfig.vercel.app with TLS certificate validation disabled (rejectUnauthorized: false) and passes the response body to new Function('require', data.toString())(require), executing the fetched payload with access to the installer's require at npm install time. The destination is a mutable, non-registry, non-publisher host unrelated to the package's advertised purpose. Package metadata presents the module as a Node.js runtime monitoring and diagnostics toolkit and lists the placeholder author Your Name; the postinstall behavior is unrelated to the advertised monitor sources.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a66d1f02c3c943836d41a7ec92c150c5529880890a4cc502115412dddb0c519c

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-014647

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aegis-runtime-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database