Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-6411
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall data-fetching-client

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

1 flagged
0.0.1-poc

Indicators of compromise (SHA-256)

7e3b28cd7d92e52caebbbc24439e3075e592ca43dbeb5cd711d4ccb3df74c1ec
913d882d66d587abb1d6fe92b8b6d7353c1b4ae79fb175cc3f10b606dd5f8457
03fbb9ddf06fb9a7703ffa62db06f9b4b0da31ed76b0f14f662d2197d6c2d13c

Detection & response playbook

Malicious package
  1. Find 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.

  2. 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.

  3. 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.

  4. 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

No. data-fetching-client on npm has been identified as a malicious package (version 0.0.1-poc flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j99m-jc5r-9w58IN-MAL-2026-008161RLMA-2026-05526

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.

Explore

data-fetching-client (npm) malicious package — MAL-2026-6411 | O3 Security