Which versions of @torbeck/heap are malicious?

The following npm versions of @torbeck/heap are flagged malicious: 4.3.10, 4.3.11, 4.3.14. Treat any of these as compromised.

How do I remediate @torbeck/heap if I installed it?

@torbeck/heap is a typosquat — you almost certainly intended a legitimately-named package. Remove @torbeck/heap, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @torbeck/heap — how do I know if it already compromised me?

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

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

Malicious package

@torbeck/heapnpm

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

MAL-2026-10405

Immediate action

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

npm uninstall @torbeck/heap

What this malware does

@torbeck/heap impersonates the legitimate @datastructures-js/heap package: README.md line 1 reads # @datastructures-js/heap, package.json sets homepage/repository/bugs to github.com/datastructures-js/heap and author to Eyas Ranjous <[email protected]>, while the npm scope @torbeck is unrelated. The package re-exports the genuine Heap class so consumers get a working API. Appended to src/heap.js after exports.Heap = Heap; (around line 247) is a heavily obfuscated obfuscator.io payload (two rotated string-array RC4-style decoders, ~580 and ~700 entries, with Function.toString anti-tamper traps and console-method override checks). On require('@torbeck/heap') via the package's index.js main entry, the payload derives an AES key by XORing four hardcoded buffers, decrypts a hidden URL, issues an http/https.request to download a binary into os.tmpdir(), writes a PID lock and.meta.json with a sha256, chmods the file to 0755, and spawns it detached via process.execPath or bash -c with stdio:'ignore', windowsHide:true, and unref() — plus a re-exec wrapper that respawns the parent under a sentinel. Platform-specific branches handle win/linux/mac. There is no version pinning or signature check on the downloaded bytes, the URL is concealed by obfuscation, and the dropped binary's purpose is unrelated to a heap data-structure library. This is a typosquat carrying an install/require-time RCE dropper.

Malicious versions

3 flagged

4.3.104.3.114.3.14

Indicators of compromise (SHA-256)

0999453caf66088321ca8bf3347a0e2c7cc7bc835589da8b6d2c904735d1f4d4

b8f88862ffacb671bdaed8521274293d5ef20bafee0deb91cc38cd852daa6a7d

84b533170c48284483245bcf2eb3e05e1b7721ee4b40bac5328cd1466bd08b18

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @torbeck/heap (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @torbeck/heap across your stack and pipelines.
If you installed it — respond
@torbeck/heap is a typosquat — you almost certainly intended a legitimately-named package. Remove @torbeck/heap, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @torbeck/heap 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 @torbeck/heap 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. @torbeck/heap on npm has been identified as a malicious package (versions 4.3.10, 4.3.11, 4.3.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009839IN-MAL-2026-009838IN-MAL-2026-009840

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @torbeck/heap-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