Which versions of datacamp-light are malicious?

The following npm versions of datacamp-light are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate datacamp-light if I installed it?

datacamp-light establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed datacamp-light — how do I know if it already compromised me?

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

Yes — datacamp-light is associated with the IN-MAL-2026-006961, GHSA-j27q-7263-hr46 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 datacamp-light 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 datacamp-light (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datacamp-light across your stack and pipelines.

Malicious package

datacamp-lightnpm

datacamp-light is a confirmed malicious npm package (MAL-2026-6091) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in datacamp-light (npm)

MAL-2026-6091

Immediate action

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

npm uninstall datacamp-light

What this malware does

Package impersonates the DataCamp brand while shipping near-empty stub exports (index.js init/helper return trivial constants). The postinstall lifecycle hook (node install.js) runs on every npm install and collects the installer's hostname, OS username, home directory, platform, current working directory, and timestamp, then POSTs them over HTTPS to dc.iam.c.noratomo.asia/install with TLS certificate verification disabled (rejectUnauthorized: false). The destination domain has no relationship to datacamp.com. The combination of brand-impersonating name, hollow library functionality, lifecycle-triggered outbound beacon to an unrelated domain, identifying-host fields, and disabled TLS verification is a supply-chain reconnaissance implant against developers who install this expecting DataCamp tooling.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4dbdcc4ef12aca6461f8e765976a7b2b33099a1791a7aee7e353371b7954a91c

efa864017d5a67788121d9c941c58caa51db2227814dbcb858a7224b865bc698

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for datacamp-light (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datacamp-light across your stack and pipelines.
If you installed it — respond
datacamp-light establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If datacamp-light 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 datacamp-light 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. datacamp-light on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006961GHSA-j27q-7263-hr46

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks datacamp-light-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database