Which versions of originaldevelopmentstelemetry are malicious?

The following npm versions of originaldevelopmentstelemetry are flagged malicious: 1.2.2, 1.2.7. Treat any of these as compromised.

How do I remediate originaldevelopmentstelemetry if I installed it?

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

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

Yes — originaldevelopmentstelemetry is associated with the GHSA-m8hq-jrvf-g8xm, IN-MAL-2026-019186, IN-MAL-2026-019178 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 originaldevelopmentstelemetry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for originaldevelopmentstelemetry (2 malicious versions).

Malicious package

originaldevelopmentstelemetrynpm

Advisory published Aug 30, 2026Updated Aug 31, 2026

originaldevelopmentstelemetry is a confirmed malicious npm package (MAL-2026-15586) that executes malicious code on install (malicious versions 1.2.2, 1.2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in originaldevelopmentstelemetry (npm)

MAL-2026-15586

Immediate action

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

npm uninstall originaldevelopmentstelemetry

What this malware does

The package is advertised as a telemetry utility but its sole exported function, downloadAndRunClient, downloads updater.hta from raw.githubusercontent.com/Acevatex/Testprogram/main/updater.hta (an unrelated personal GitHub account, on the mutable main branch, with no pinning and no hash or signature check), writes it to a temporary path, and launches it via Windows mshta as a detached process. HTA execution grants the remote repository owner arbitrary code execution on any Windows host that invokes this function, and the fetched content can change at any time without a new package release. The stated 'telemetry' purpose is inconsistent with a Windows HTA runner, and the author metadata is a generic 'originaldevelopments' identity.

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

2 flagged

1.2.21.2.7

Indicators of compromise (SHA-256)

49b20cbdf4a18dbb40dab15e915cee25b8961e2bea6e12f4424dbef89f5e2526

60940a80ca72863b54a3cc8f1cc7da49be77b38e9111d4cb77cfc1417671f399

97c9d6d214df15c3af4969c562f75b43a43dec13857d3ba30cd6858ffd804f58

Detection & response playbook

Malicious package

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

Campaign

GHSA-m8hq-jrvf-g8xmIN-MAL-2026-019186IN-MAL-2026-019178

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks originaldevelopmentstelemetry-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