Which versions of pkg-telemetry-r4f9 are malicious?

The following npm versions of pkg-telemetry-r4f9 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate pkg-telemetry-r4f9 if I installed it?

pkg-telemetry-r4f9 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 pkg-telemetry-r4f9 — how do I know if it already compromised me?

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

Yes — pkg-telemetry-r4f9 is associated with the IN-MAL-2026-006900, GHSA-755p-5wm7-4qg5 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 pkg-telemetry-r4f9 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 pkg-telemetry-r4f9 (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 pkg-telemetry-r4f9 across your stack and pipelines.

Malicious package

pkg-telemetry-r4f9npm

pkg-telemetry-r4f9 is a confirmed malicious npm package (MAL-2026-5990) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pkg-telemetry-r4f9 (npm)

MAL-2026-5990

Immediate action

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

npm uninstall pkg-telemetry-r4f9

What this malware does

On install, package.json's postinstall hook runs node run.js, which loads beacon scripts that combine child_process, os, and http modules to collect host identifiers and send them to a remote endpoint. beacon_linux.js reads os.hostname() and os.platform() and issues an http.request POST carrying that data to a hardcoded host. beacon17.js similarly imports child_process and performs outbound HTTP GETs. The package name ("pkg-telemetry-r4f9" with a random-looking suffix) and its install-time-only behavior are inconsistent with any legitimate library purpose. Installing this package causes automatic, unconsented exfiltration of installer host metadata and provides a remote-execution surface via child_process.

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)

decf727db779a7cc4017b0bd8000f9fb40bcc5c6d93b016144a94e245886ea4e

9f31644aae73e457753525f73778a8704bb48c27bbbcdb819ef2a4c7e78e2cc7

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pkg-telemetry-r4f9 (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 pkg-telemetry-r4f9 across your stack and pipelines.
If you installed it — respond
pkg-telemetry-r4f9 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 pkg-telemetry-r4f9 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 pkg-telemetry-r4f9 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. pkg-telemetry-r4f9 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-006900GHSA-755p-5wm7-4qg5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pkg-telemetry-r4f9-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