Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in bigops-tinkoff-telephony-mock

Malware was discovered in the npm package bigops-tinkoff-telephony-mock. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • bigops-tinkoff-telephony-mock

The npm package bigops-tinkoff-telephony-mock was found to contain malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.\n\nThe malware grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given the level of system access the malware appears to have obtained.

Indicators of compromise

Packages
  • bigops-tinkoff-telephony-mock

Remediation

  • Immediately remove the bigops-tinkoff-telephony-mock package from all systems
  • Rotate all secrets, keys, and credentials from a different, unaffected computer
  • Perform a full security audit and malware scan of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if compromise is suspected

Sources

  1. GitHub Advisory GHSA-92wj-cj5h-gp6p · GitHub Advisory Database

Cite this entry

"Malware in bigops-tinkoff-telephony-mock." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bigops-tinkoff-telephony-mock-1bqpwa

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in epic-common-node (npm)

    The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.

    npmCompromised package
  2. containedcritical

    Malicious code in epic-common (npm)

    The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.

    npmCompromised package
  3. containedcritical

    Malware in leb128x

    The npm package leb128x was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  4. containedcritical

    Malicious code in checkout-desktop-total (npm)

    The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.

    npmCompromised package