Which versions of incommincentives are malicious?

The following npm versions of incommincentives are flagged malicious: 2.2.0, 2.2.1, 2.2.2. Treat any of these as compromised.

How do I remediate incommincentives if I installed it?

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

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

Yes — incommincentives is associated with the GHSA-r7x8-ww27-72mm, RLMA-2025-05392, RLUA-2025-05813 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 incommincentives 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 incommincentives (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging incommincentives across your stack and pipelines.

Malicious package

incommincentivesnpm

incommincentives is a confirmed malicious npm package (MAL-2025-47992) that executes malicious code on install (malicious versions 2.2.0, 2.2.1, 2.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in incommincentives (npm)

MAL-2025-47992

Immediate action

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

npm uninstall incommincentives

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

3 flagged

2.2.02.2.12.2.2

Indicators of compromise (SHA-256)

6f82fa02afa9a50bf4a03e925b89a63789fd1df25ff1031b9e6598f16b3880e8

73e217e61cac745c6c6b30d52b138271fa66aa6de600efc7044f726ca507e859

db40f51400b8865eec183fafe2ada0efde77a7dea10f7cc951ed09eb63949d00

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

Campaign

GHSA-r7x8-ww27-72mmRLMA-2025-05392RLUA-2025-05813

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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