Which versions of fed-callnative are malicious?

The following npm versions of fed-callnative are flagged malicious: 99.9.1, 99.9.2. Treat any of these as compromised.

How do I remediate fed-callnative if I installed it?

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

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

Yes — fed-callnative is associated with the GHSA-hwp4-g2h4-2v7r, RLMA-2026-05089, RLUA-2026-05538 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 fed-callnative 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 fed-callnative (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fed-callnative across your stack and pipelines.

Malicious package

fed-callnativenpm

fed-callnative is a confirmed malicious npm package (MAL-2026-5668) that executes malicious code on install (malicious versions 99.9.1, 99.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fed-callnative (npm)

MAL-2026-5668

Immediate action

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

npm uninstall fed-callnative

What this malware does

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

2 flagged

99.9.199.9.2

Indicators of compromise (SHA-256)

3971b7c0ac52c7cb668a8147d9774cb0f7a0b4e0bf04a59a6b55426f9c84fcf4

9ec8616134175c643635247a771cf4a5ffaea4c6f1e3de9e35beefe76cfd5f25

57da656ea7b795239a38873360d6842ca1801261257d2f6017b66aae9a787995

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

Campaign

GHSA-hwp4-g2h4-2v7rRLMA-2026-05089RLUA-2026-05538

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fed-callnative-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