Which versions of chameleon-src are malicious?

The following npm versions of chameleon-src are flagged malicious: 6.6.29. Treat any of these as compromised.

How do I remediate chameleon-src if I installed it?

Remove chameleon-src 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.

I already installed chameleon-src — how do I know if it already compromised me?

If chameleon-src 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.

Is chameleon-src part of a known attack campaign?

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

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

Malicious package

chameleon-srcnpm

chameleon-src is a confirmed malicious npm package (MAL-2026-14202) that executes malicious code on install (malicious version 6.6.29). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chameleon-src (npm)

MAL-2026-14202

Immediate action

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

npm uninstall chameleon-src

What this malware does

The package's preinstall lifecycle runs examples/verify.js, which invokes init() defaulting to a hardcoded Sentry DSN (o4510485815754752.ingest.us.sentry.io project 4511805473488896). verify.js calls setUserFromPublicIp() to fetch https://www.cloudflare.com/cdn-cgi/trace and parse the installer's public IP, attaches it as the Sentry event user, deliberately throws inside check() to force an exception capture, and awaits flush(5000) to ensure upload before process exit. Because init() is configured with sendDefaultPii:true, the hostname (server_name) is also attached. Every npm install of this package therefore uploads the installer's public IP and hostname to the author's Sentry project without consent, opt-in, or a caller-configurable destination on the install path. The package's one-line description and name ("chameleon-src") do not disclose telemetry collection.

Malicious versions

1 flagged

6.6.29

Indicators of compromise (SHA-256)

170070f9183f8660c8ab51246ab146d6f03af25dcb6fb027ca73624619d098bc

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chameleon-src (version 6.6.29). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chameleon-src across your stack and pipelines.
If you installed it — respond
Remove chameleon-src 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.
Did it already run?
If chameleon-src 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.
How O3 protects you
O3 blocks chameleon-src 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. chameleon-src on npm has been identified as a malicious package (version 6.6.29 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018280

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chameleon-src-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database