Which versions of @afetcan/storage are malicious?

The following npm versions of @afetcan/storage are flagged malicious: 0.0.27. Treat any of these as compromised.

How do I remediate @afetcan/storage if I installed it?

@afetcan/storage 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.

I already installed @afetcan/storage — how do I know if it already compromised me?

If @afetcan/storage 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 @afetcan/storage across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @afetcan/storage (version 0.0.27).

Malicious package

@afetcan/storagenpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@afetcan/storage is a confirmed malicious npm package (MAL-2025-191180) that steals credentials and exfiltrates sensitive data (malicious version 0.0.27). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @afetcan/storage (npm)

MAL-2025-191180

Immediate action

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

npm uninstall @afetcan/storage

What this malware does

The package @afetcan/storage 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.27

Indicators of compromise (SHA-256)

6185482e2a1647e6f4e6383ce2aa50d651187f6a3f821328d87e13ae342af5bd

4abbde27cce56326711e4e32f42572cb60977ca7ccce4ebf1fcfa558a847c1a6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @afetcan/storage (version 0.0.27).
If you installed it — respond
@afetcan/storage 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.
Did it already run?
If @afetcan/storage 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. @afetcan/storage on npm has been identified as a malicious package (version 0.0.27 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/storage-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

Explore

All malware advisories How O3 detects malware Vulnerability database