Which versions of runtime-sentinel are malicious?

The following npm versions of runtime-sentinel are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

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

Remove runtime-sentinel 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 runtime-sentinel — how do I know if it already compromised me?

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

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

Malicious package

runtime-sentinelnpm

runtime-sentinel is a confirmed malicious npm package (MAL-2026-12432) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in runtime-sentinel (npm)

MAL-2026-12432

Immediate action

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

npm uninstall runtime-sentinel

What this malware does

The package's postinstall script (src/test.js) issues an HTTPS GET to https://workconfig.vercel.app with TLS certificate verification disabled (rejectUnauthorized: false), and passes the response body directly to new Function('require', data)(require). This executes attacker-controlled code with full Node.js require access on the installer's machine at npm install time. The remote content is unpinned, unverified, and served from a mutable third-party host; whatever bytes the endpoint returns run on the installer. The package presents itself as a runtime monitoring toolkit and ships generic placeholder author metadata (Your Name), which does not match the postinstall behavior.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

9ab7fe9b1d524fefdba9c46d4857cad10abac9de2b31584472043bb1fc526e35

f44234b49595ac2b15e3b5249920f7ff64cf897b7543da959e95621814948da1

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 runtime-sentinel (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging runtime-sentinel across your stack and pipelines.
If you installed it — respond
Remove runtime-sentinel 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 runtime-sentinel 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 runtime-sentinel 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. runtime-sentinel on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014883IN-MAL-2026-014696

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks runtime-sentinel-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