What does the sickle-wrapper malware do?

The OpenSSF Package Analysis project identified 'sickle-wrapper' @ 0.2.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of sickle-wrapper are malicious?

The following npm versions of sickle-wrapper are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate sickle-wrapper if I installed it?

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

If sickle-wrapper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find sickle-wrapper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sickle-wrapper (version 0.2.0).

Malicious package

sickle-wrappernpm

Advisory published May 19, 2026Updated May 20, 2026

sickle-wrapper is a confirmed malicious npm package (MAL-2026-4178) that executes malicious code on install (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sickle-wrapper (npm)

MAL-2026-4178

Immediate action

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

npm uninstall sickle-wrapper

What this malware does

The OpenSSF Package Analysis project identified 'sickle-wrapper' @ 0.2.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

cf0ce8be09572968ecc56d1879825b49624c7346a7391f203ea27e9ed0805674

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sickle-wrapper (version 0.2.0).
If you installed it — respond
Remove sickle-wrapper 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 sickle-wrapper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sickle-wrapper-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