Which versions of @frostnode/probe are malicious?

The following npm versions of @frostnode/probe are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @frostnode/probe if I installed it?

@frostnode/probe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @frostnode/probe — how do I know if it already compromised me?

If @frostnode/probe 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 @frostnode/probe part of a known attack campaign?

Yes — @frostnode/probe is associated with the IN-MAL-2026-007292 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 @frostnode/probe 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 @frostnode/probe (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @frostnode/probe across your stack and pipelines.

Malicious package

@frostnode/probenpm

Malicious code in @frostnode/probe (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6304

Immediate action

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

npm uninstall @frostnode/probe

What this malware does

No suspicious behaviors were observed in this package version. There are no install-time lifecycle hooks fetching or executing remote code, no credential or environment scraping, no hardcoded attacker-controlled endpoints, and no silent-relay patterns in the package's code paths.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a143792d6fce9dfc36bbd2f99c44710055d4f0be6408ed046fb4ea4ea2e86f3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @frostnode/probe (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @frostnode/probe across your stack and pipelines.
If you installed it — respond
@frostnode/probe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @frostnode/probe 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 @frostnode/probe 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. @frostnode/probe on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007292

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @frostnode/probe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring