Which versions of sieve2workers are malicious?

The following npm versions of sieve2workers are flagged malicious: 1.0.0, 5.0.0. Treat any of these as compromised.

How do I remediate sieve2workers if I installed it?

Remove sieve2workers 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 sieve2workers — how do I know if it already compromised me?

If sieve2workers 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 sieve2workers part of a known attack campaign?

Yes — sieve2workers is associated with the GHSA-jv2g-mmjm-vgfg, RLMA-2025-05511, RLUA-2025-05948 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 sieve2workers 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 sieve2workers (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sieve2workers across your stack and pipelines.

Malicious package

sieve2workersnpm

sieve2workers is a confirmed malicious npm package (MAL-2025-48081) that executes malicious code on install (malicious versions 1.0.0, 5.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sieve2workers (npm)

MAL-2025-48081

Immediate action

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

npm uninstall sieve2workers

What this malware does

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

2 flagged

1.0.05.0.0

Indicators of compromise (SHA-256)

d53786bf7b79fe2302460c7f8c369195321ca0da5736f4c4da00ca4a42a45529

df74d97349bfac600e8a9aa69b25f133c5284ff15d7d4acebb6f4a17c7a9ee2c

22d63780d17326c60e6529ed97dfb2c3d8df659ab3f4195ac55231b73cd485a8

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 sieve2workers (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sieve2workers across your stack and pipelines.
If you installed it — respond
Remove sieve2workers 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 sieve2workers 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 sieve2workers 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. sieve2workers on npm has been identified as a malicious package (versions 1.0.0, 5.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jv2g-mmjm-vgfgRLMA-2025-05511RLUA-2025-05948

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sieve2workers-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

Explore

All malware advisories How O3 detects malware Vulnerability database