Which versions of woltpickerapp are malicious?

The following npm versions of woltpickerapp are flagged malicious: 40.6.2. Treat any of these as compromised.

How do I remediate woltpickerapp if I installed it?

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

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

Yes — woltpickerapp is associated with the GHSA-cp44-cvhx-wf33, RLMA-2026-01833, RLUA-2026-02062 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 woltpickerapp 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 woltpickerapp (version 40.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging woltpickerapp across your stack and pipelines.

Malicious package

woltpickerappnpm

Malicious code in woltpickerapp (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1973

Immediate action

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

npm uninstall woltpickerapp

What this malware does

The package woltpickerapp was found to contain malicious code.

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

40.6.2

Indicators of compromise (SHA-256)

b0c8234f6a72b4da77be49eb19f15dc41dd1d94b6b8b9bc4bffd3ef9ddb4316b

8a6352ffe541b2fd35eb37ebb5dbdc78f1f57a51d31b36c6fcae39d21f97c594

dfe3c58b7ad6737f65fe20d852f76cc8e92f47ad27cd2c8d641524c48d287693

8ed4b7f8b423ed6c708c0088c8386c95ef6b52a2c1d7e1df3059b3e701f74165

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

Campaign

GHSA-cp44-cvhx-wf33RLMA-2026-01833RLUA-2026-02062

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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