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

execfencesnpm

execfences is a confirmed malicious npm package (MAL-2026-10118) that executes malicious code on install (malicious versions 5.0.2, 5.0.3, 5.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in execfences (npm)

MAL-2026-10118
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall execfences

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

7 flagged
5.0.25.0.35.0.45.0.55.0.65.1.05.1.1

Indicators of compromise (SHA-256)

a3fb71704b8be7cfa2ba47ff5ae9c4f4a32312fabe52e416036575507e6893fe
974c5744c98a462c30d6c8dd3ca078461dc172244203e85d5290fa05660d2d1c
a62d48ece42be28785bfa48cc15f331b03c72135805bba38a32ebef058dc5c9b
36726aba2cdbbb6deb7fd6fb6bce79f96c24caaf7fe6f293429d0f0fa052f41b
51f6927a175368705bb9e3dbf8a173fd5894a4f0b7d4751fc1a5c241e0b87c95
566e80682725410ec5741a421d12451e47887d1406a359068ba33c8240dab2ea
5f6e08eceb35c700aa389e53efe622afa774ad58ba364daa0802595da4af83e5
7e071b19f0b2fd3cd752eaf9d815b08af6e6234371ade1fa87a324732fa75d98

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

  2. If you installed it — respond

    Remove execfences 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 execfences 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 execfences 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. execfences on npm has been identified as a malicious package (versions 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.1.0, 5.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-34gj-pgfv-8qgfIN-MAL-2026-009816IN-MAL-2026-009813IN-MAL-2026-009814IN-MAL-2026-009818IN-MAL-2026-009819IN-MAL-2026-009817IN-MAL-2026-009815

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks execfences-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.

Explore

execfences (npm) malicious package — MAL-2026-10118 | O3 Security