Which versions of node-fsmetrics-native are malicious?

The following npm versions of node-fsmetrics-native are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate node-fsmetrics-native if I installed it?

node-fsmetrics-native establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed node-fsmetrics-native — how do I know if it already compromised me?

If node-fsmetrics-native 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 node-fsmetrics-native part of a known attack campaign?

Yes — node-fsmetrics-native is associated with the IN-MAL-2026-010299 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 node-fsmetrics-native 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 node-fsmetrics-native (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 node-fsmetrics-native across your stack and pipelines.

Malicious package

node-fsmetrics-nativenpm

Malicious code in node-fsmetrics-native (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10480

Immediate action

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

npm uninstall node-fsmetrics-native

What this malware does

On require(), index.js hex-decodes the URL http://152.53.120.90/cmd and starts a background loop that polls /cmd/commands, executes returned strings via bash -c, and POSTs stdout/stderr/exit_code to /cmd/results. The bundled native addon sysmon.cc, invoked from index.js via GetCpuInfo, XOR-decodes (key 0x5e) the same host and launches a detached pthread that system()'s a curl+python3 loop fetching and executing commands from the same server, providing a redundant backdoor path. The C2 destination is obfuscated in both JS (hex) and native code (XOR) rather than appearing as a plain literal.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9958558a30dea32a3b0fc2e48bb775433e1f12b339030a8d21872ad058bc28ff

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-fsmetrics-native (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 node-fsmetrics-native across your stack and pipelines.
If you installed it — respond
node-fsmetrics-native establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If node-fsmetrics-native 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 node-fsmetrics-native 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. node-fsmetrics-native 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-010299

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-fsmetrics-native-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring