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

@afetcan/apinpm

Malicious code in @afetcan/api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191179
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @afetcan/api

What this malware does

The package @afetcan/api was found to contain malicious code.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
0.0.13

Indicators of compromise (SHA-256)

fa915cfff470cee0e001515013e5dc3e91ef7461760e0e6df54188d6bea2c130
a0a79aa802450fc62bcdf8bdb70d6619752f6db790e68472e80016d5893111ba

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @afetcan/api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @afetcan/api 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 @afetcan/api 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. @afetcan/api on npm has been identified as a malicious package (version 0.0.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @afetcan/api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring