rustsec-2026-0039
Vulnerability from osv_rustsec
Published
2026-03-10 12:00
Modified
2026-03-10 20:34
Summary
`chrono_anchor` was removed from crates.io due to malicious code
Details

The chrono_anchor crate attempted to exfiltrate .env files to a server that was in turn impersonating the legitimate timeapi.io service.

The malicious crate had 1 version published on 2026-03-04 approximately 6 days before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.

Thanks to Socket for reporting this crate. They have published a blog post about this recent campaign, and we advise users of timeapi.io to exercise caution when using crates to interact with that service.


{
  "affected": [
    {
      "database_specific": {
        "categories": [],
        "cvss": null,
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "chrono_anchor",
        "purl": "pkg:cargo/chrono_anchor"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "The `chrono_anchor` crate attempted to exfiltrate `.env` files to a server that\nwas in turn impersonating the legitimate `timeapi.io` service.\n\nThe malicious crate had 1 version published on 2026-03-04 approximately 6 days\nbefore removal and had no evidence of actual downloads. There were no crates\ndepending on this crate on crates.io.\n\nThanks to [Socket][socket] for reporting this crate. They have published\n[a blog post][blog] about this recent campaign, and we advise users of\n`timeapi.io` to exercise caution when using crates to interact with that\nservice.\n\n[socket]: https://socket.dev\n[blog]: https://socket.dev/blog/5-malicious-rust-crates-posed-as-time-utilities-to-exfiltrate-env-files",
  "id": "RUSTSEC-2026-0039",
  "modified": "2026-03-10T20:34:44Z",
  "published": "2026-03-10T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/chrono_anchor"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2026-0039.html"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "`chrono_anchor` was removed from crates.io due to malicious code"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…