Which versions of ftm-noderpc are malicious?

The following npm versions of ftm-noderpc are flagged malicious: 0.0.1-security, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.13, 1.0.14, 1.0.15, 1.0.16. Treat any of these as compromised.

How do I remediate ftm-noderpc if I installed it?

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

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

Yes — ftm-noderpc is associated with the GHSA-m2jq-q4v9-276f, RLMA-2026-01332 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 ftm-noderpc 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 ftm-noderpc (16 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ftm-noderpc across your stack and pipelines.

Malicious package

ftm-noderpcnpm

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

MAL-2026-520

Immediate action

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

npm uninstall ftm-noderpc

What this malware does

The package ftm-noderpc was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

16 flagged

0.0.1-security1.0.01.0.11.0.21.0.31.0.41.0.61.0.71.0.81.0.91.0.101.0.111.0.131.0.141.0.151.0.16

Indicators of compromise (SHA-256)

b2c3dc311c3d101881ee473edd9232f94c95686770a45f681038070507407fc2

48bffc97a9e30f15aaeea633df39ff0ab500a8f4aeee9757390e0d0e2393e9d9

bb0e324cc5b128b09c298f130569f83ddc026a44467a249b45e8414804c64610

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

Campaign

GHSA-m2jq-q4v9-276fRLMA-2026-01332

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ftm-noderpc-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