Which versions of @torbeck/priority-queue are malicious?

The following npm versions of @torbeck/priority-queue are flagged malicious: 6.3.6, 6.3.7, 6.3.9. Treat any of these as compromised.

How do I remediate @torbeck/priority-queue if I installed it?

Remove @torbeck/priority-queue 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.

I already installed @torbeck/priority-queue — how do I know if it already compromised me?

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

Yes — @torbeck/priority-queue is associated with the IN-MAL-2026-010294, IN-MAL-2026-010296, IN-MAL-2026-010295 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/priority-queue 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/priority-queue (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/priority-queue across your stack and pipelines.

Malicious package

@torbeck/priority-queuenpm

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

MAL-2026-10472

Immediate action

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

npm uninstall @torbeck/priority-queue

What this malware does

The package republishes @datastructures-js/priority-queue verbatim — identical README pointing to datastructures-js.info, the original author 'Eyas Ranjous', and the upstream repository URL git+https://github.com/datastructures-js/priority-queue.git — under an unrelated @torbeck scope. Its package.json (L33-34) declares "dependencies": { "@datastructures-js/heap": "npm:@torbeck/[email protected]" }, using npm alias syntax to silently substitute the legitimate @datastructures-js/heap with a sibling package @torbeck/[email protected] published by the same untrusted maintainer. src/priorityQueue.js does require('@datastructures-js/heap'), so on every import the substituted @torbeck/heap is loaded in place of the upstream package. The installer-facing harm is the namespace-abuse mechanism itself: any consumer who installs @torbeck/priority-queue automatically pulls @torbeck/heap under a name that reads as the legitimate datastructures-js dependency, regardless of what the @torbeck/heap tarball currently contains. The actual payload, if any, lives in @torbeck/heap and must be analyzed in its own record.

Malicious versions

3 flagged

6.3.66.3.76.3.9

Indicators of compromise (SHA-256)

08cb928626dd6143e55ace3665c91ce2e51d54edadda1c91ca24685ec12e06fc

21cbe2ff5c8605c7c7cfe7c19d69f8096a0f271714f085102f1f0e9f5ebec3b6

b3109ebd719fa91812bd69e50b418b78f2a04c5478924f6ff53054cb798dc937

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @torbeck/priority-queue (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/priority-queue across your stack and pipelines.
If you installed it — respond
Remove @torbeck/priority-queue 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 @torbeck/priority-queue 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/priority-queue 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/priority-queue on npm has been identified as a malicious package (versions 6.3.6, 6.3.7, 6.3.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010294IN-MAL-2026-010296IN-MAL-2026-010295

References

Credits

Amazon Inspector · finder

Detect & block this

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