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

feature-flag-servicenpm

Malicious code in feature-flag-service (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3253
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall feature-flag-service

What this malware does

The package feature-flag-service was found to contain malicious code.

The OpenSSF Package Analysis project identified 'feature-flag-service' @ 2.0.3 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged
2.0.22.0.3

Indicators of compromise (SHA-256)

69173384cc716a5a94e29e7abd367e903fcb600836a9c0a5f5c656236b2fd803
876fa5645622fb575a15d1c6e437fd3bfe86737223af0439befec4bb6c1f2670
9ba3fb4537827a604de645ffad07771bc9f7ed4e1f4a70b16b4c35effadcf744

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 feature-flag-service (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging feature-flag-service across your stack and pipelines.

  2. If you installed it — respond

    Remove feature-flag-service 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 feature-flag-service 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 feature-flag-service 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. feature-flag-service on npm has been identified as a malicious package (versions 2.0.2, 2.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks feature-flag-service-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.

feature-flag-service (npm) malicious package — MAL-2026-3253 | O3 Security