Which versions of 1co are malicious?

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

How do I remediate 1co if I installed it?

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

If 1co 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 1co part of a known attack campaign?

Yes — 1co is associated with the IN-MAL-2026-002223 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 1co across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 1co (version 1.0.1).

Malicious package

1conpm

Advisory published May 12, 2026Updated May 13, 2026

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

Malicious code in 1co (npm)

MAL-2026-3671

Immediate action

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

npm uninstall 1co

What this malware does

The package's main entry (index.js) exports a console replacement whose.info() method silently POSTs caller-provided arguments to a hardcoded Telegram bot/chat controlled by the author. This is reachable on first use of the primary API, not merely at install. A sibling _index.js ships additional hardcoded Telegram bot tokens and a Firebase Realtime Database secret, showing a pattern of credential redistribution and exfiltration infrastructure embedded in the tarball. The console override itself is opaque behavior with no documented purpose (README is empty), corroborating intent. Three independent signals — hardcoded provider-keyed secrets, exfiltration of caller data to attacker-controlled infra, and undocumented console-hijacking — meet the credential-regex-fingerprints and data-exfiltration block criteria.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

e09cc40cc6a0084f383fd0a359be04fa0d0e5aed50e9f4b78d8714868fc35ca4

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-002223

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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