What does the dependencykfee-2 malware do?

The OpenSSF Package Analysis project identified 'dependencykfee-2' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of dependencykfee-2 are malicious?

The following npm versions of dependencykfee-2 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dependencykfee-2 if I installed it?

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

If dependencykfee-2 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 dependencykfee-2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dependencykfee-2 (version 1.0.0).

Malicious package

dependencykfee-2npm

Advisory published Oct 29, 2026Updated Nov 2, 2026

dependencykfee-2 is a confirmed malicious npm package (MAL-2026-18460) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dependencykfee-2 (npm)

MAL-2026-18460

Immediate action

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

npm uninstall dependencykfee-2

What this malware does

The OpenSSF Package Analysis project identified 'dependencykfee-2' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bb75f6ebc23c1e1ea6fc3ae422db80b65e8f9b8d7c21faa2de9c58ba049e9d89

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dependencykfee-2 (version 1.0.0).
If you installed it — respond
Remove dependencykfee-2 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 dependencykfee-2 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. dependencykfee-2 on npm has been identified as a malicious package (version 1.0.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 dependencykfee-2-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