Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

okfe-serverless-confnpm

Malicious code in okfe-serverless-conf (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2646
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall okfe-serverless-conf

What this malware does

The package okfe-serverless-conf 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
9999.1.0

Indicators of compromise (SHA-256)

269594c1529d0ee52a3d3ac7022f11c67a2a3b1a0751ad58efe545cf72567ba3
add9c9c3996a516171fe17826581f26e2bc84d41a011598239b995980f2e86c9
f74a72b0853bd9a530292e0f2f74d820ea396dd35650bb3537cf4b2d8705e0dc

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for okfe-serverless-conf (version 9999.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging okfe-serverless-conf across your stack and pipelines.

  2. If you installed it — respond

    Remove okfe-serverless-conf 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.

  3. Did it already run?

    If okfe-serverless-conf 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.

  4. How O3 protects you

    O3 blocks okfe-serverless-conf 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. okfe-serverless-conf on npm has been identified as a malicious package (version 9999.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-974m-p83h-567hRLMA-2026-02007

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks okfe-serverless-conf-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.