data-fetching-clientnpm
data-fetching-client is a confirmed malicious npm package (MAL-2026-6411) that executes malicious code on install (malicious version 0.0.1-poc). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in data-fetching-client (npm)
What this malware does
Package self-identifies in its package.json description as a bug-bounty dependency-confusion proof-of-concept against an internal package name of the same identifier. On install, postinstall.js reads os.hostname() and the current timestamp and prints them to local stdout with a '[hubspot-poc]' marker; no network call is made and no data leaves the host. The harm in this version is limited to demonstrating that the public-registry package would resolve in place of the targeted internal package in a misconfigured build environment. The shape is a namespace-confusion publication: any consumer whose registry resolution is misconfigured would execute the author's postinstall code, and a non-PoC successor version could trivially replace the local log with arbitrary install-time behavior.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for data-fetching-client (version 0.0.1-poc). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging data-fetching-client across your stack and pipelines.
If you installed it — respond
Remove data-fetching-client 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 data-fetching-client 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 data-fetching-client 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks data-fetching-client-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.