Which versions of init-router are malicious?

The following npm versions of init-router are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate init-router if I installed it?

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

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

Yes — init-router is associated with the RLMA-2025-06365, RLUA-2026-01353 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 init-router 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 init-router (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging init-router across your stack and pipelines.

Malicious package

init-routernpm

Malicious code in init-router (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192803

Immediate action

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

npm uninstall init-router

What this malware does

The package init-router was found to contain malicious code.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

030bd01686162e88a70c6036c21aedaaafb115ed74516ba93338d345d18942ff

0d018c8963d1a91fc672bfe128a7699635fb3dd34a7df393119baee24d44a3d0

311d6164d4a3d0848081d514d7a7df50220d42cd9b2f56df2c75992f24d3d686

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

Campaign

RLMA-2025-06365RLUA-2026-01353

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks init-router-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