Which versions of real-router-utils are malicious?

The following npm versions of real-router-utils are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate real-router-utils if I installed it?

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

If real-router-utils 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 real-router-utils part of a known attack campaign?

Yes — real-router-utils is associated with the IN-MAL-2026-019353 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 real-router-utils 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 real-router-utils (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 real-router-utils across your stack and pipelines.

Malicious package

real-router-utilsnpm

real-router-utils is a confirmed malicious npm package (MAL-2026-15825) 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 real-router-utils (npm)

MAL-2026-15825

Immediate action

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

npm uninstall real-router-utils

What this malware does

package.json declares a preinstall script that runs an inline node command reading the installer's OS hostname, username, and current working directory and sending them as query parameters to a hardcoded webhook.site collector URL (https://webhook.site/e32d3b8a-a5df-40cc-ae60-7a8343b581e4). The request fires automatically on npm install, before any user interaction, and the destination is an anonymous ephemeral webhook endpoint unrelated to any documented package purpose.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f91fd520ae94997277ef7d591d30dc728b895611fd45b890e2ec1a68233e29a8

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 real-router-utils (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 real-router-utils across your stack and pipelines.
If you installed it — respond
Remove real-router-utils 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 real-router-utils 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 real-router-utils 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. real-router-utils 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-019353

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks real-router-utils-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