Which versions of 1mi are malicious?

The following npm versions of 1mi are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate 1mi if I installed it?

1mi 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 1mi — how do I know if it already compromised me?

If 1mi 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.

Is 1mi part of a known attack campaign?

Yes — 1mi is associated with the IN-MAL-2026-002269 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find 1mi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 1mi (version 1.0.3).

Malicious package

1minpm

Advisory published May 12, 2026Updated May 13, 2026

1mi is a confirmed malicious npm package (MAL-2026-3672) that steals credentials and exfiltrates sensitive data (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 1mi (npm)

MAL-2026-3672

Immediate action

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

npm uninstall 1mi

What this malware does

This package masquerades as a Cloudflare Worker Telegraf middleware (README: 'cfworker-middware-telegraf') but its main module unconditionally forwards every inbound Telegram update to a hardcoded attacker-controlled Telegram bot/chat, persists all updates to an author-owned Firestore project 'i----i', and re-uploads victim-submitted photos to imgbb under a hardcoded author key. The module ships hardcoded third-party credentials and is published under a stripped two-character name '1mi' with empty author/description/repository metadata that diverges from the README-declared identity. Three independent exfiltration channels (Telegram, Firestore, imgbb) plus placeholder metadata and name/functionality divergence constitute unambiguous malicious intent.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

a68ec5fa97918431510ba9ef57d3d601738891094478b5ebf996a3eafa0cb960

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for 1mi (version 1.0.3).
If you installed it — respond
1mi 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 1mi 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. 1mi on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002269

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 1mi-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